Systems and methods for collaboration

ABSTRACT

In some embodiments, the disclosed systems and methods provide a client-server infrastructure capable of supporting a variety of asynchronous and synchronous collaboration activities in a so-called collaboration place. Some of these activities include chatting, viewing and/or editing one or more data files, and sharing one or more applications, data files, and/or displays. The client-server infrastructure supports seamless navigation between the supported asynchronous and synchronous activities in the collaboration place. Additionally, the client-server architecture supports data persistence, so that data files associated with the collaboration place can be stored for subsequent access.

REFERENCE TO RELATED APPLICATION

This application claims priority under 35 U.S.C. § 119(e) to U.S. PatentApplication Ser. No. 60/607,388 filed on Sep. 3, 2004, the contents ofwhich application are expressly incorporated by reference herein intheir entirety.

COPYRIGHT NOTICE

The present application includes material that is subject to copyrightprotection. The copyright owner does not object to the facsimilereproduction of the application by any person as the application appearsin the records of the U.S. Patent and Trademark Office, but otherwisereserves all rights in the copyright.

FIELD

The general field is in the field of collaboration systems and methods.The particular fields of application include enterprise software,productivity software tools, online conferencing, network collaborationsoftware, instant messaging, real-time collaboration applications, andoffice software applications.

BACKGROUND

Traditionally, people who were separated by geographic distances and whodesired to collaborate with each other in so-called “real time” hadrelatively few options. An expensive option included traveling to acommon geographic location or place to meet, chat, share notes, anddiscuss ideas. A less expensive, but arguably less productive, optionincluded participating in a telephone conference call and concurrentlyexchanging email messages.

However, companies are just beginning to fully realize that phone ande-mail are no longer the most efficient ways for communication intoday's disperse organizations. Currently the market of collaborationconsists of a variety of companies offering a variety of separatesolutions. The capabilities of these known solutions include: presence,instant messaging, web conferencing and team or project workspaces. Inthe current market, vendors can only offer stand-alone products for eachof these solutions. Solutions are generally limited in scope to addresseither asynchronous collaboration or synchronous collaboration. Knownattempts to combine synchronous and asynchronous collaboration haveprovided awkward solutions because they require leaving one mode inorder to act in the other mode.

A drawback of these solutions is that each is a separate application andthe use of these software on a separate basis is cumbersome,complicated, and expensive. For example, in current workspaceapplications, more than one person can view a document in the samevirtual environment, but these technologies only offer serial editing,allowing only a single individual to make edits to the document whenthat individual has that document open on his or her computer. As such,while collaborating in a serial editing environment, people are onlyallowed to edit one at a time. Each edit must be discussed over instantmessaging or e-mail and collaborators must wait to make edits. Thus, insuch systems, the permission to edit the document must be passed backand forth as if they were writing on the same piece of paper with onepen. Such techniques can result in ending that momentum that can comewith successful collaboration sessions.

Another application commonly used for collaboration is E-mail. However,companies are finding that e-mail is overwhelming their organizations.Companies are complaining of losing hours of productivity a day tosorting through e-mail. Another example of a conventional collaborationtool is instant messaging (IM), otherwise referred to herein as chat. IMis typically implemented using peer-to-peer communications. Chat is atransit real-time or “live” activity in which interface activity issynchronously updated as the interaction progresses. Prior knownattempts to combine synchronous IM-type tools with asynchronouscollaboration tools, such as browser-based conferencing tools, haveresulted in cumbersome products that often require users to leave one ofthe modes of communication to enter the other of the modes ofcommunication.

Another example of a conventional collaboration tool is browser-basedconferencing. Such on-line conferencing activity is typically atransient event. In some known systems, static recordings of thesessions are recorded for later replay. One drawback of such systems isthe inability to provide features for continued collaboration, resumingcollaboration, or sharing asynchronous collaboration on the samesubject.

Concurrently using a number of stand-alone collaboration tools, such ascombinations of one or more of the previously described tools and/or oneor more other available tools, leads to inevitable problems. Forexample, compatibility problems and productivity losses are inevitablewhen using several separate stand-alone collaboration tools.Transferring information from one tool to another tool can often resultin data files or edits being lost, permissions being incorrectlyupdated, and/or sessions or connections being dropped. Switching fromone stand-alone application to another stand-alone application so that acollaboration can “move” from IM, to a browser-based conference, and toa shared workspace can waste valuable time and frustrate collaborationparticipants.

Therefore, it would be beneficial to provide improved systems andmethods for collaboration, which for example can overcome theillustrative drawbacks of existing collaboration tools mentioned orprovide new functionality to users.

SUMMARY

In accordance with the principles of the present invention, systems andmethods for collaboration and related features are provided. Acollaboration application can be implemented to provide collaborationtools and features to users. The application can be implemented within aclient-server environment to, for example, provide seamless synchronousand asynchronous collaboration comprising a central persistent databasefor a particular project and seamless integration of synchronous andasynchronous collaboration tools. A collaboration place can beimplemented on a server and/or in combination with client computers.

In accordance with the principles of the present invention, acollaboration place, when referred to herein, means collaborationsoftware that has at least the characteristics of being persistent,addressable, and capable of holding more than one data file. Forexample, a collaboration place can be an addressable persistent set(i.e., more than just one) of data files accessible by at least twousers simultaneously, in which data introduced by one user is madeavailable to other allowed users based on update(s) via a back channeland not requiring selection of “refresh” as in a browser-based system.Users may interact with the application through a collaboration placeinterface (e.g., a desktop application). As used herein, a collaborationplace interface can be understood to be part of a collaboration place.

As used herein, seamless refers to the elimination or absence of one ormore intervening user-required steps, and preferably all user requiredsteps, to move from one type of collaboration tool to another (e.g., adesktop application containing different types of collaboration tools,no separate log-in, no launching of a separate application). Seamlesscan also refer to the implementation of a plurality of collaborationtools and unifying data (e.g. in a things window, as further describedherein) in a collaboration place.

A plurality of different types of collaboration is preferably supported(e.g., chat, content editing, conferencing, meetings, documentversioning, etc.). In one aspect, the software is implemented to provideusers with freedom to move or escalate to additional types ofcollaboration tools when working in a first collaboration tool. Featurescan be implemented to gradually or gracefully escalate to this greaterenvironment.

For example, one or more requests (e.g., from a first client and secondclient) can be received by a server to establish a collaboration place.Based on the one or more requests, a collaboration place can beestablished (e.g., by the server). Network connections are implementedbetween the collaboration place and the one or more users who requestedthe collaboration place (e.g., the first and second clients). Thecollaboration place is implemented to be associated with collaborationplace interfaces executing on the user's platform (e.g., the first andsecond clients) wherein the collaboration place interfaces include aprimary display for presenting a primary type of data and are configuredfor being escalated based on a request from the users (e.g., theirrespective clients) to include at least one secondary display forpresenting a secondary type of data. The primary type of data can, forexample, include data related to at least one of a chat application andan instant messenger application. The secondary type of data can, forexample, include data related to at least one of an application forprocessing audio data, an application for processing graphic data, anapplication for processing multimedia data, an application forprocessing text data, and an application for processing video data.Another feature may involve escalating, based on receiving a requestfrom a first client, one of the collaboration place interfaces toinclude a secondary display for presenting data related to the clientsconnected to the collaboration place and/or related to at least one ofan application for processing audio data, an application for processinggraphic data, an application for processing multimedia data, anapplication for processing text data, and an application for processingvideo data. In another aspect, based on receiving a request from thefirst client, the one of the collaboration place interfaces can beescalated to include a secondary display for presenting data related todata files associated with the collaboration place.

Escalation can occur in a user's collaboration place interface toinclude a secondary display based on a request from another user'scollaboration place interface. In another feature, pulling an objectinto a collaboration place interface can synchronously escalate othercollaboration place interfaces connected to the same collaborationplace. Additional displays can be displayed in the collaboration placeinterfaces to implement different collaboration tools. A residentapplication can be implemented to provide the collaboration placeinterface to provide secondary displays for collaboration. A window forobjects associated with the place can be displayed along with a chatwindow in each of the collaboration place interfaces. A private placemay be implemented as part of a collaboration place interface and thecollaboration place. A database may be associated with the collaborationof the clients in the collaboration place. Objects related to a placecan be stored and accessed from the collaboration place interfaces forlater resumption of collaboration. Information on activity in the placecan be recorded and made available through the database.

Co-editing can be a feature that is implemented as part of acollaboration application, for example, as part of a collaborationplace. Co-editing can, for example, be provided by implementing asoftware resident application (e.g., a desktop application) configuredto provide and integrate a plurality of collaboration tools on aplurality of user platforms, establishing communications via a pluralityof Internet connections between the software resident applications and aserver that supports collaboration among users, administeringinteractions in another application implemented on the user platformsvia the server, synchronizing activity in the other application via backchannel connection of the Internet connections dedicated to pushingcontent to the software resident application; and storing informationrelated to the activity on the server. The software resident applicationcan be configured to implement a collaboration place. (As used herein,unless otherwise indicated by context, the term software residentapplication can be understood to include a client software applicationor a client-resident software application as those terms are understoodby those of ordinary skill in the art.) The administering can includemanaging sequential co-editing activity among the users. If desired, theadministering can include managing simultaneous co-editing activityamong the users. The storing can include storing user identifierinformation. If desired, the storing can include storing a history ofinteractions. Access to the stored information is provided to the userwho participated in the interaction for later retrieval of that storedinformation. A software development kit for the software residentapplication can be distributed to provide a framework for independentlyimplementing such cooperative activity.

A private interface can be implemented as part of a collaborationapplication, for example, as part of a collaboration place. A privateinterface can, for example, be implemented by providing a collaborationapplication configured to provide integrated collaboration tools to aplurality of users through network-connected user platforms, providing aprivate interface configured for private use by a user when the user isin an interface for one of the collaboration tools, and moving contentfrom the private place to the interface when directed by the user andstoring the content for later retrieval by other users. The privateinterface can be privately displayed for the user when the user isinteracting with different collaboration tools of the collaborationapplication. The private interface is preferably displayed inconjunction with a collaboration place in which the user is acollaborator. The system or method is configured to provide a user withthe authority to provide guest access to another user to have temporaryaccess to a portion of the private interface. A list of collaborationplaces related to the user can be displayed in the private interface.Visual cues can be displayed in association with items in the list. Thevisual cues can include information on an upcoming meeting. If desired,content is stored in the private interface based on the user's pastinteraction with the collaborative application. In another aspect, thecollaborative application is configured to be responsive and to supporta user's selecting an icon of another user and dragging and dropping theicon into the private place (e.g., to provide that user withtemporary/guest access to the personal interface).

A time-line feature can be provided in a collaboration application, forexample, as part of a collaboration place. Such a feature can, forexample, be provided by implementing a collaboration tool through whichnetworked users collaborate asynchronously, storing artifacts of thecollaboration in a database associated with a particular instance of thecollaboration tool, providing access to the database to the usersthrough the collaboration tool so that artifacts can be manipulated, anddisplaying a user-selectable option for viewing a previous state of oneor more of the artifacts. If desired the collaboration tool includes acollaboration place. An associated feature can be to implement a playerthat plays information on how one, more than one, and/or all of theartifacts evolved over time.

A collaboration application may include a feature for providing“peripheral vision” to one or more users by informing users of activitywithin a collaborative application. Such information can be related tonumber of users, roles of users, the existence of meeting, etc. Forexample, peripheral vision can be provided by providing a database forstoring data associated with two or more independent collaborationplaces, administering collaboration activities among participatingclients in each of the two or more independent collaboration places,generating activity data for each of the two or more independentcollaboration places based on administering the collaborationactivities, receiving a request from a requesting client for theactivity data for one or more of the two or more independentcollaboration places, and based on the request, providing the activitydata to the requesting client for presentation in a collaboration placeinterface. Other forms of peripheral vision can also be implemented.

Other features can, for example, also include persistence of a tool, aplace, or a database dedicated to a place, polling, content sharing,voice conferencing, video, meeting related features, activity threads,workflows and templates, indexing, place presence, integration ofenterprise document management software with collaboration tools,worldview, “drag-and-drop” features, access, and security.

Some aspects of the systems and methods of embodiments the presentinventions can include: drag and drop escalation, enhancement ofinterface from a “non-collaborative space” to a “live” collaborativespace with tools or options that are gradually added based on thecollaboration, enhancement of interface from a relatively simple livecollaborative space to a relatively complex live collaborative spacewith tools or options that are gradually added based on thecollaboration, a seamless blend of synchronous and asynchronouscollaboration, integrated platform for viewing and editing documents andfor synchronous and asynchronous collaboration that adds functionalityon a gradual basis as collaboration progresses, implementation of toolsor changes to a user's environment based on the attributes of a person,group, document, or application that is “dragged” into the environment,reversal of escalation, template based escalation, and escalation toaudio (e.g., telephone, Voice over Internet Protocol (VoIP)), video, orother audio-video content.

These and other features of the systems and methods described herein canbe more fully understood by referring to the following detaileddescription and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Features of the invention, its nature, and various advantages will beapparent from the following detailed description, taken in conjunctionwith the accompanying drawings in which:

FIG. 1A schematically illustrates an exemplary system for supporting aplace in accordance with one embodiment of the present invention;

FIG. 1B schematically illustrates exemplary data for supporting a placein accordance with one embodiment of the present invention;

FIG. 2A is a functional block diagram of an illustrative system diagramin accordance with one embodiment of the present invention;

FIG. 2B is a functional block diagram of an illustrative system serverin accordance with one embodiment of the present invention;

FIG. 2C is a functional block diagram of an illustrative system clientin accordance with one embodiment of the present invention;

FIG. 2D is a functional block diagram of illustrative system serversockets in accordance with one embodiment of the present invention;

FIGS. 3A-3G schematically illustrate exemplary displays of acollaboration tool in accordance with one embodiment of the presentinvention;

FIG. 4 schematically illustrates an embodiment of a method forestablishing a new place in accordance with one embodiment of thepresent invention;

FIGS. 5A-5C schematically illustrate an embodiment of a method forproviding access to a previously established place in accordance withone embodiment of the present invention;

FIG. 6 schematically illustrates exemplary collaboration activities thatcan be performed in a place in accordance with one embodiment of thepresent invention;

FIG. 7 schematically illustrates an embodiment of a method forgenerating an instant meeting in a place in accordance with oneembodiment of the present invention;

FIGS. 8A and 8B schematically illustrate an embodiment of a method foradministering content sharing in a place in accordance with oneembodiment of the present invention;

FIG. 9A schematically illustrates an embodiment of a method foradministering consecutive content editing in a place in accordance withone embodiment of the present invention;

FIG. 9B schematically illustrates an embodiment of a method forextending a collaboration application in accordance with one embodimentof the present invention;

FIG. 9C schematically illustrates an embodiment of a method foradministering collaboration in an application through an Internetconnected server for a collaboration application in accordance with oneembodiment of the present invention;

FIGS. 9D-F schematically illustrate embodiments of screen shots andinteractivity for implementing co-editing in accordance with oneembodiment of the present invention;

FIG. 10 schematically illustrates an exemplary system for supportingvoice communications in a place in accordance with one embodiment of thepresent invention;

FIG. 11 schematically illustrates exemplary types of data persistencesupported in a place in accordance with one embodiment of the presentinvention;

FIGS. 12A-E provide illustrative examples of embodiments of the presentinvention in accordance with one embodiment of the present invention;

FIG. 12F provides a chart illustrating escalation and de-escalationfeatures in accordance with one embodiment of the present invention;

FIG. 13A schematically illustrates an embodiment of a method for atimeline view feature in accordance with one embodiment of the presentinvention;

FIGS. 13B and 13C schematically illustrate an embodiment of an interfaceproviding a timeline feature in accordance with one embodiment of thepresent invention;

FIG. 14A schematically illustrates an embodiment of a method for apersonal place feature in accordance with one embodiment of the presentinvention;

FIG. 14B schematically illustrates an embodiment of a method for apersonal place feature providing visual cues to a user in accordancewith one embodiment of the present invention;

FIGS. 14C and 14D schematically illustrates interfaces for a personalplace feature in accordance with one embodiment of the presentinvention;

FIG. 15 schematically illustrates an embodiment for peripheral visionfeature in accordance with one embodiment of the present invention; and

FIG. 16 schematically illustrates an interface for providing peripheralvisions in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION

Illustrative embodiments will now be described to provide an overallunderstanding of the systems and methods for collaboration describedherein. One or more examples of the illustrative embodiments are shownin the drawings. The disclosed systems and methods can be adapted andmodified to provide systems and methods for other applications, and thatother additions and modifications can be made to the disclosed systemsand methods without departing from the scope of the present disclosure.For example, features of the illustrative embodiments can be combined,separated, interchanged, and/or re-arranged to generate otherembodiments. Such modifications and variations are intended to beincluded within the scope of the present disclosure.

Systems and methods of the present invention provide next generationcollaboration and related features. In one aspect, collaboration will bea seamless blend of presence, conferencing, and teamware functionalitybacked by a repository of appropriate size such as an enterprise-classrepository. As such, a true unified collaboration application can beprovided to users for enterprise collaboration. In some embodiments,systems and methods that implement a seamless blend of synchronous andasynchronous collaboration or implement synchronous collaboration in thecontext of a enterprise-class Enterprise Content Management (“ECM”)store are provided.

In one embodiment, systems and methods are implemented that provideseamless integration of each of the solutions mentioned above (and/or adesired combination thereof): presence, instant messaging, webconferencing, standard document management functionality (check-in,check-out, document sharing, etc), or team or project workspaces.Separate environments (e.g., each separate environment integrated in thecollaboration application) can work together in a full collaborativeeffort. For example, documents can be opened during an initialconversation over IM and then easily dragged from the repository intothe workspace, where simultaneous co-editing can begin while each userviews the document in real time. As mentioned above, in knownconventional systems, work has to be passed back and forth and eachedited version is then manually and/or automatically saved back to aremote server.

Another feature that can be implemented to add asynchronouscharacteristics to these synchronous characteristics is thatconversations (e.g., all conversations in the application) are savedregardless of what environment the conversation occurs in. Theapplication is configured to identify who it came from, when, whatprogram, regarding what project. This can be important information inbusinesses that deal with compliance. User activity is automaticallytracked for them and information is stored and managed to track activityin the application to maintain tracking and information on allinteractions, downloads, viewing, conferences, IM's, etc. Bothsynchronous and asynchronous activity (e.g., communications) is trackedand available for viewing. The tracking can extend to all types ofsynchronous and asynchronous communications, which may includeconversations, meetings, IMs, VoIP, etc., but is not limited to suchactivity. An advantage of synchronized collaboration backed by a storeof activity related information is that information or activity can allbe maintained in context.

Another feature is the implementation of the ability of the applicationto interact with users through graceful escalation of the userinterface. For example, this provides the users with the ability togracefully escalate a conversation within the same application. Aconversation can be taken from voice to video conferencing withoutjumping from one application to another or any other environment change.Another example is a two-person IM escalating to a multi-persondiscussion thread.

In some embodiments, the disclosed systems and methods provide aclient-server infrastructure capable of supporting a variety ofasynchronous and synchronous collaboration activities in a unifiedvirtual environment. Some of these activities include chatting, viewingand/or editing one or more data files, and sharing one or moreapplications, data files, and/or displays. The client-serverinfrastructure supports seamless navigation between the supportedasynchronous and synchronous activities. Additionally, the client-serverarchitecture supports data persistence, so that at least data files thatare viewed, edited, and/or otherwise accessed in the collaboration placeduring a collaboration activity can be stored for subsequent access.

In some embodiments of the disclosed systems and methods, a serverreceives requests from clients for accessing (e.g., logging or enteringinto) a previously established place. In reply, the server provides dataassociated with the place to the clients via a place interface, forms anetwork connection among the clients, and mediates interactions amongthe clients in the place. While they are logged into the place, theclients can share content with each other via the server. For example,in some of such embodiments, the clients can concurrently display and/ormodify data files via the place interface. As further described herein,the data files can include audio data files, video data files, documentswith text and/or graphics, multimedia presentations, and/or other typesof data files. The server associates the place with a place identifierand other types of place data, such as client identifiers and datafiles. Based on detecting a termination event, the server stores theplace identifier and the data associated therewith for subsequent accessby the clients (e.g., for provision to clients in reply to subsequentrequests to access the place).

FIG. 1A schematically illustrates an exemplary system for supporting aplace. As shown in FIG. 1A, the exemplary system 100 includes one ormore client digital data processing devices 120 (“clients”), one or moreserver digital data processing devices 140 (“servers”), and one or moredatabases 150. The clients 120, servers 140, and databases 150communicate using one or more data communications networks 110(“networks”).

In FIG. 1A, the features in a digital data processing device are shownas residing in client 120. If desired, one or more features of client120 can be implemented as part of server 140.

Generally, references herein to a client and a server are used todifferentiate two communicating devices and/or sets of processorinstructions. References herein to a client and/or a server can thus beunderstood to be references to communications originating from a clientand/or a server as these terms are understood by those of ordinary skillin the art. Such communications can be based on or otherwise initiatedfrom one or more input devices (e.g., a keyboard, a stylus, a mouse,etc.) controlled by a user. Also, references herein to a client and/or aserver can thus be understood to include one or moreprocessor-controlled devices that act in a client-server (i.e.,request-response) model, in which the client and the server can resideon the same processor-controlled device, and in which, based onperspective, the client can act as a server, and the server can act as aclient. More generally, references herein to a client can be understoodto include computer software and/or hardware.

As shown in FIG. 1A, a user 102 ₁ desiring to access a place can executeone or more software application programs 104 residing on the client 120to generate data messages that are routed to, and/or receive datamessages generated by, one or more software application programs 108(e.g., programs for establishing a new place and/or administering apreviously established place) residing on server 140 via network 110. Adata message includes one or more data packets, and the data packets caninclude control information (e.g., addresses of the clients and servers120 and 140, names and/or identifiers of the software applicationprograms 104 and 108, etc.) and payload data (e.g., data relevant to arequest 138 to establish a new place or access a pre-existing place,such as a place identifier for the pre-existing place).

The software application programs 104 can include one or more softwareprocesses (e.g., a calculation process or engine) executing within oneor more memories 118 of the client 120. Similarly, the softwareapplication programs 108 can include one or more software processesexecuting within one or more memories of the server 140.

The software application programs 108 can include one or more sets ofinstructions and/or other features that enable the server 140 to, forexample, establish a place, regulate access to the place, and mediateinteractions between user 102 ₁ and user 102 _(M) while logged into theplace via clients 120(1) and 120(M). As described herein, the softwareapplication programs 104 and 108 can include instructions forauthenticating users 102, authorizing users 102 (e.g., to access aplace), and otherwise processing places (e.g., establishing places andadministering interactions between users 102 logged into the place). Thesoftware application programs 104 and 108 can be provided using acombination of built-in features of one or more commercially availablesoftware application programs and/or in combination with one or morecustom-designed software modules. Although the features and/oroperations of the software application programs 104 and 108 aredescribed herein as being executed in a distributed fashion (e.g.,operations performed on the networked client and servers 120 and 140),those of ordinary skill in the art will understand that at least some ofthe operations of the software application programs 104 and 108 can beexecuted within one or more digital data processing devices that beconnected by a desired digital path (e.g., point-to-point, networked,data bus, etc.).

The digital data processing device 120 and 140 can include a personalcomputer (PC), a computer workstation (e.g., Sun, Hewlett-Packard), alaptop computer, a server computer, a mainframe computer, a handhelddevice (e.g., a personal digital assistant (PDA), a Pocket PC™, acellular telephone, an e-mail device (e.g., a Blackberry™, a Clie™, or aTrio™ e-mail device), etc.), an information appliance, and/or anothertype of generic or special-purpose, processor-controlled device capableof receiving, processing, and/or transmitting digital data. Processor114 refers to the logic circuitry that responds to and processesinstructions that drive digital data processing devices such as, withoutlimitation, a central processing unit, an arithmetic logic unit, anapplication specific integrated circuit, a task engine, and/orcombinations, arrangements, or multiples thereof.

Instructions for programs 104 or other executables can be pre-loadedinto a programmable memory that is accessible to the processor 114and/or can be dynamically loaded into/from one or more volatile (e.g.,RAM, cache, etc.) and/or non-volatile (e.g., a hard drive, optical disk,etc.) memory elements communicatively coupled to the processor 114. Theinstructions can, for example, correspond to the initialization ofhardware within the digital data processing devices 120 and 140, anoperating system 116 that enables the hardware elements to communicateunder software control and enables other computer programs tocommunicate, and/or software application programs 104 and 108 that aredesigned to perform operations for other computer programs, such asoperations relating to establishing and administering a place. Theoperating system 116 can support single-threading and/ormulti-threading, where a thread refers to an independent stream ofexecution running in a multi-tasking environment. A single-threadedsystem is capable of executing one thread at a time, while amulti-threaded system is capable of supporting multiple concurrentlyexecuting threads and can perform multiple tasks simultaneously.

Local user 102 can interact with client 120 by, for example, viewing acommand line, using a graphical and/or other user interface, andentering commands via an input device, such as a mouse, a keyboard, atouch sensitive screen, a stylus, a track ball, a keypad, etc. The userinterface can be generated by a graphics subsystem 122 of the client120, which renders the interface into an on- or off-screen surface(e.g., on display device 126 and/or in a video memory). Inputs from theuser 102 can be received via an input/output (I/O) subsystem 124 androuted to processor 114 via an internal bus (e.g., system bus) forexecution under the control of the operating system 116.

Similarly, a remote user can interact with the digital data processingdevices 120 and 140 over the network 110. The inputs from the remoteuser can be received and processed in whole or in part by a remotedigital data processing device collocated with the remote user.Alternatively and/or in combination, the inputs can be transmitted backto and processed by the local client 120 or to another digital dataprocessing device via one or more networks using, for example, thinclient technology. The user interface of the local client 120 can alsobe reproduced, in whole or in part, at the remote digital dataprocessing device collocated with the remote user by transmittinggraphics information to the remote device and instructing the graphicssubsystem of the remote device to render and display at least part ofthe interface to the remote user. Network communications between two ormore digital data processing devices can include a networking subsystem128 (e.g., a network interface card) to establish the communicationslink between the devices. The communications link that interconnects thedigital data processing devices can include elements of a datacommunications network, a point to point connection, a bus, and/oranother type of data path.

In one illustrative operation, the processor 114 of the client 120executes instructions associated with software application programs 104(including, for example, runtime instructions specified, at leastpartially, by the local user 102 and/or by another software applicationprogram, such as a batch-type program) that can instruct the processor114 to at least partially control the operation of the graphicssubsystem 122 in rendering and displaying a graphical user interface(including, for example, one or more menus, windows, and/or other visualobjects) on the display device 126.

The network 110 can include a series of network nodes (e.g., the clients120 and servers 140) that can be interconnected by network devices andwired and/or wireless communication lines (e.g., public carrier lines,private lines, satellite lines, etc.) that enable the network nodes tocommunicate. The transfer of data (e.g., messages) between network nodescan be facilitated by network devices, such as routers, switches,multiplexers, bridges, gateways, etc., that can manipulate and/or routedata from an originating node to a server node regardless ofdissimilarities in the network topology (e.g., bus, star, token ring),spatial distance (e.g., local, metropolitan, wide area network),transmission technology (e.g., TCP/IP, Systems Network Architecture),data type (e.g., data, voice, video, multimedia), nature of connection(e.g., switched, non-switched, dial-up, dedicated, or virtual), and/orphysical link (e.g., optical fiber, coaxial cable, twisted pair,wireless, etc.) between the originating and server network nodes.

FIG. 1A shows processes 130, 132, 134, and 136. A process refers to theexecution of instructions that interact with operating parameters,message data/parameters, network connection parameters/data, variables,constants, software libraries, and/or other elements within an executionenvironment in a memory of a digital data processing device that causesa processor to control the operations of the digital data processingdevice in accordance with the desired features and/or operations of anoperating system, a software application program, and/or another type ofgeneric or specific-purpose application program (or subparts thereof).For example, network connection process 130 and 132 refers to a set ofinstructions and/or other elements that enable the digital dataprocessing devices 120 and 140 to establish a communication link andcommunicate with other digital data processing devices during one ormore sessions. A session refers to a series of transactions communicatedbetween two network nodes during the span of a single networkconnection, where the session begins when the network connection isestablished and terminates when the connection is ended. Databaseinterface process 134 refers to a set of instructions and other elementsthat enable the server 120 to access the database 150 and/or other typesof data repositories to obtain access to, for example, user data 142,place data 144, and place rules 148. The accessed information can beprovided to the software application program 108 for further processingand manipulation. Administrative process 136 refers to a set ofinstructions and other features that enable the server 120 to monitor,control, and/or otherwise administer a place. For example, theadministrative process 136 can (i) maintain and update configuration,runtime, and/or session data for the one or more digital data processingdevices 120, 140 and/or the software application programs 104 or 108executing on the devices 120, 140, (ii) provide buffer management,multi-threaded services, and/or data structure management, (iii) provideinitialization parameters to the digital data processing devices 120,140 and/or the software application programs 104, 108, (iv) managegroups of objects (e.g., groups of data elements stored on the digitaldata processing devices 120, 140 and/or stored or otherwise maintainedin the database 150, groups of software application programs 104, 108,groups of users authorized to access software application programs 104or 108, groups of licenses, etc.), (v) manage relationships betweenobjects in response to messages communicated between digital dataprocessing devices 120 and 140, (vi) provide support services (e.g.,encryption and/or decryption, compression, path routing, messageparsing, message format manipulation, etc.) to the digital dataprocessing devices 120 and 140, and/or (vii) provide load balancingbased on, for example, processor usage/availability, networkusage/availability, memory usage/availability, software applicationprogram usage/availability, message length, and/or message volume.

Although the illustrated processes 130, 132, 134, and 136 and theirfeatures are described as being separate, the illustrated processesand/or their features can be combined into one or more processes ifdesired. One or more of the illustrated processes 130, 132, 134, and 136can be provided using a combination of built-in features of one or morecommercially available software application programs and/or incombination with one or more custom-designed software modules.

The databases 150 can be stored on a non-volatile storage medium or adevice known to those of ordinary skill in the art (e.g., compact disk(CD), digital video disk (DVD), magnetic disk, internal hard drive,external hard drive, random access memory (RAM), redundant array ofindependent disks (RAID), or removable memory device). As shown in FIG.1, the databases 150 can be located remotely from the client 120 andserver 140. In some embodiments, the databases 150 can be locatedlocally to client 120 or server 140 and/or can be integrated into client120 or server 140, respectively. The databases 150 can includedistributed databases. The databases 150 can include different types ofdata content and/or different formats for stored data content. Forexample, the databases 150 can include tables and/or other types of datastructures.

FIG. 1B schematically illustrates exemplary data for supporting a place.As shown in FIG. 1B, the exemplary data 200 includes user data 210,place data 250, and place rules 280.

User data 210 includes user identifiers 215, user place data 220, useraccount data 240, user friend data 245, and user data files 248. Useridentifiers 215 include data identifying the name and login informationof each user of system 100. Usually, the login information includes auser identifier and associated authorization information for accessingsystem 100. The user identifier can include a numeric, an alphabetic, oran alphanumeric identifier, such as a username and/or an email address.The authorization information can include a password or passphraseand/or one or more types of biometric data unique to the user (e.g., aretinal scan, a thumb print, a voice sample, etc.). In some embodiments,the authorization information also includes data identifying a servercapable of supporting one or more places in system 100 (e.g., server140), such as, but not limited to, an Internet Protocol (IP) or othernetwork address of the server and/or a domain name. In some embodiments,user identifiers 215 include contact information for the users of system100. The contact information can be based on a wireless and/or a wiredcommunication network and can include one or more of email addresses,regular/postal (i.e., non-electronic) mail addresses, and telephonenumbers (e.g., cellular telephone numbers and landline telephonenumbers).

User place data 220 include user place identifiers 225, datarepresenting the on-line status 230 of the user, and skin data 235.Place identifiers 225 include data identifying the names of the placeswhich the user has been authorized to access. The on-line status data230 includes an on-line indicator that indicates whether a user hasentered and/or otherwise accessed an active place (e.g., logged into anactive place). In some embodiments, the on-line indicator includes a bitor flag that is set based on whether the user has entered a place.Usually, if a user has entered a place, the on-line status data 230(and/or other data in user data 210) also includes the IP or othernetwork address of the client 120 associated with the user for loggingand/or debugging purposes. In some embodiments, the on-line status data230 includes an activity indicator that represents a type and/or adegree of user activity in a place. For example, the activity indicatorcan include a binary busy/idle indicator that represents a period ofactivity/inactivity in the place (e.g., idle for the previous 10seconds). Also for example, the activity indicator can include acomplex, e.g., non-binary, indicator that can identify user activityinside and/or outside the place. Such a complex activity indicator canidentify an active display or window on client 120 (e.g., a display orwindow into which data is currently being (and/or has recently been)entered and/or otherwise provided by a user input device) and a typeand/or a degree of activity in the active display or window (e.g., 100keystrokes per minute in an active word processing window).

User account data 240 includes credits and debits associated with useraccounts, such as credits based on payments from the user and debitsbased on purchases by the user (e.g., purchases of access to and/orprivileges within a place). Purchases can be made on an item-by-itembasis (e.g., a rate per unit of time logged into a place) or,alternatively, on a subscription basis (e.g., a flat fee for unlimitedaccess to a place in a time period). In some embodiments, user accountdata 240 can include information related to transactions between users102 and system 100 (e.g., places which a user 102 visited, units of timeelapsed during those visits, etc.). As will be understood by those ofordinary skill in the art, the disclosed systems and methods can beimplemented with free (e.g., wide-open) access as an alternative to payaccess.

User friend data 245 includes data identifying the friends of users ofsystem 100. The friends of a user are other users with whom the userdesires to correspond, collaborate, or otherwise interact in one or moreplaces. The friend identifiers can include alphabetic, numeric, and/oralphanumeric identifiers, such as usernames and email addresses. In someembodiments, based on detecting the entrance of user 102 into system100, server 140 can alert and/or otherwise notify the user friends thatthe user 102 has entered the system (e.g., transmit messages to theclients 120 associated with those friends). For example, in oneembodiment, server 140 can provide a friend notification display forpresentation in the place interface and/or in the active displays of theclients 120 of the user friends. Alternatively and/or in combination, insome embodiments, based on detecting the entrance of user 102 into anactive place, server 140 can alert and/or otherwise notify the userfriends in the active place that the user has entered the place.

Place data 250 includes data representing the features of places thatare supported by system 100. Place data 250 includes place identifiers255, place data files 260, place log files 275, place interface datafiles 265, and place participant identifiers 270. Generally, places canhave one of two states, specifically, active or dormant, which statesare determined based on whether the places are currently beingadministered by server 140 (e.g., based on whether one or more users arecurrently logged into the places). As further described herein, eachplace is associated with a place identifier 255, and each placeidentifier 255 is associated with one or more place data files 260, oneor more place log files 275, one or more place interface data files 265,and one or more place participant identifiers 270. The place identifiers255 include data identifying the names of the places supported by system100. The place identifiers 255 can include alphabetic, numeric, and/oralphanumeric identifiers that can be at least partially chosen and/orotherwise determined by users of system 100

Each place interface data file 265 includes data identifying features ofthe place interface corresponding to a place identifier 225. Aspreviously indicated herein, server 140 can provide data to clients 120via a place interface, form a network connection among the clients 120,and mediate interactions among the clients 120. A place interface caninclude a display and/or one or more sub-displays, and each display andeach sub-display can include one or more check boxes, one or moreresponse boxes, one or more radio buttons, one or more pull-down menus,one or more icons, and/or one or more other visual objects thatfacilitate collaboration. (An exemplary place interface is shown in FIG.3D.) Usually, a place interface includes a primary display (e.g., awindow) and one or more secondary or sub-displays therein (e.g.,secondary or sub-windows), in which each secondary display supports adifferent collaboration activity or a feature of a place. In someembodiments, the secondary displays are configured for presenting databased on one or more of the place data files 260, the place log files275, and the place participant identifiers 270 associated with placeidentifier 255. Each place interface data file 265 thus includes datarepresenting the type, number, and organization of displays andsub-displays in the place interface corresponding to place identifier225.

In some embodiments, the originator of place (e.g., client 120 thatfirst establishes a new place) selects and/or otherwise determines thedefault features of the place interface, such as the type, number, andorganization of displays included in the interface and/or the type,number, and organization of applications included in a system tray ofthe place interface.

Alternatively and/or in combination, in some embodiments, thelook-and-feel of the place interface of client 120 can be customized byend user 102. As shown in FIG. 1B, user place data 220 includes skindata 235, which includes user selections and/or determinations ofcustomizable features of place interfaces. The customizable features caninclude sizes of displays and sub-displays; locations and organizationof sub-displays within a display; font colors, sizes, and types;background colors and types; and/or other features known to those ofordinary skill in the art. Generally, each client 120 authorized toaccess a place can customize the place interface by which it interactswith server 140 and other clients 120.

Each place data file 260 includes data files that can be displayed,modified, and/or otherwise manipulated by one or more clients 120(consecutively and/or concurrently) via a place interface correspondingto a place identifier. As further described herein, in most embodiments,place data files 265 are associated with a place identifier based on theuploading of those files into the corresponding place interface by aclient 120 (e.g., based on detecting dragging-and-dropping actions bythe client 120). As used herein, the term data files can be understoodto include files having types and formats of data known to those ofordinary skill in the art. For example, the term data files can includeapplication files, data files, executable files, object files, programfiles, operating system files, registry files, and other types of datafiles known to those of ordinary skill in the art. In some embodiments,the place data files 260 include one or more of audio data files, videodata files (e.g., still and/or animated video files), documentsincluding text and/or graphics, and multimedia presentations (e.g.,presentations, such as a slide show, that include a combination of theforegoing types of data files).

Generally, the place data files 260 are accessible (e.g., are able to beaccessed, viewed, and/or otherwise modified) by all users in a place,regardless of which user uploaded the data files 260 into the place. Assuch, the place data files 260 are public data files.

In contrast, user data files 248 are accessible by default by only asingle user. As such, user data files 248 are private data files. Asfurther described herein, the disclosed systems and methods provide anoffice utility via the place interface. In most embodiments, a user canassociate one or more data files with the corresponding office utilitybased on uploading those data files into the utility. The uploaded datafiles are associated with the user identifier 215 of the user and arestored in user data files 248. The user data files 248 can be accessedby default only by the uploading user. In some embodiments, theuploading user can designate the user data files as public data files.For example, in some of such embodiments, the uploading user can copyand/or otherwise transfer one or more of the user data files 248 to theplace data files 260 associated with a place identifier 255.

Place log files 275 include data that is generated by the disclosedsystems and methods based on interactions between clients in a placecorresponding to place identifier 255. As further described herein, insome embodiments, clients 120 can share data files and/or exchange chatmessages with each other in a place, and server 140 can generate placelog files 275 that can include, among other things, data representingthe manipulation of the shared data files (such as the types ofmanipulation by clients 120) in the file and/or transcripts of theexchanged chat messages in the place. The place log files 275 can beprovided to clients 120 upon subsequent access to the place.

Place participant identifiers 270 include data identifying theauthorized participants of places supported by system 100. Theauthorized participants of a place are determined based on the schemesdescribed herein. Place participant identifiers 270 also include dataidentifying the present participants in (i.e., participants logged into,signed into, or otherwise entered into) an active place.

Place rules 280 include rules for establishing new place 285, rules forre-establishing pre-existing place 290, and rules for administeringplace 295. As described further herein, the rules for establishing newplace 285 include rules for determining the features of the place (e.g.,participants, data files, etc.); the rules for re-establishing apre-existing place 290 include rules for identifying the placeidentifier 255 of the place, accessing stored place data 250 that isassociated with the place identifier 255, and providing the place data250 to clients 120 via a place interface; and the rules foradministering a place 295 include rules for authenticating and otherwiseauthorizing clients to participate in a place and administeringasynchronous and synchronous interactions among clients 120 in theplace, such as exchanging of chat messages or sharing of content.

Other advantageous features are also provided and illustrativelydescribed herein. Examples of systems and methods for collaboration thatimplement TCP/IP or that include object based implementations areillustratively shown in FIGS. 2A-2D. Systems and methods forcollaboration as illustratively described herein can be implementedusing a standard client/server model (FIG. 1) using, for example, TCP/IPas the transport mechanism. The server is, for example, a Java-basedserver that runs inside an Apache Tomcat container. The server is, forexample, configured to maintain a list of active client sessions socketsfor new clients, maintain the information store, and broadcast changeand request notifications to clients as appropriate.

The server is, for example, configured to maintain a list of activeclient sessions, and their related collaboration objects. A“collaboration object” can include any object in the system thatcoordinates, facilitates, or otherwise tracks the actions of theparticipants and can reference a particular meeting or conference orcollaboration (synchronous and/or asynchronous).

Collaboration places (e.g., each collaborative place initiated) cantrack which collaboration objects a client has open on their desktop.Open collaboration objects implicitly define the set of eventnotifications that a client would be interested in. In addition, theserver has a distinguished identifier for each client connected so thatother clients may easily direct specific messages to specificindividuals (e.g., IM). The distinguished identifier may be specific toa person. Whenever a change happens in a collaboration object, theserver notifies all of the other clients that are in that collaborationobject of the event. Possible event notifications include:

-   -   content added, deleted, moved, renamed, or deleted,    -   screen sharing initiated, stopped, updated,    -   person entered, exited, idled, disconnected,    -   chat message added,    -   meeting started, stopped, suspended, postponed, updated

The systems and methods of FIGS. 2A-2D can be implemented using asoftware language such as, but not limited to, Java and C#. C# is thecomponent-oriented development language for creating XML Web servicesand Microsoft .NET-connected applications for Windows and the Web. Theuser, when installing or launching the client, indicates the address (IPaddress or domain name) of the system server they wish to use forcommunication. Examples of computer platforms for a system server andclient for implementing collaboration are illustratively shown in FIGS.2B and 2C.

Communications in support of collaboration can be configured indifferent ways. For example, as shown in the example of FIG. 2D, theclient opens two sockets to the server, called the front channel and theback channel. As shown, the front channel is used for normalrequest/response interactions with the server. The client makes arequest of the server and the return value is returned in the responsepacket. These requests are all synchronous although they may haveoptional return values. The back channel is used for the server to pushevent notifications to the client. These happen asynchronously to anyother activity on the client and can occur at any time. If desired, theclient never writes to the back channel, only reads from it. In someembodiments, the back channel is a secondary TCP connection forasynchronous updates transmitted from the server to the client.

Other techniques, such as to use more than two sockets or to bothreceive and transmit on two or more socket connections can be used.Alternatively and/or in combination with a back channel connection, insome embodiments, the disclosed systems and methods can be implementedwith polling (e.g., periodic, continuous, etc.) to provide updates fromthe server to the client. For example, in some of such embodiments,polling can be used to provide updates when a back channel connection isnot available (e.g., in scenarios in which a firewall or other networksecurity device prevents direct connection to a client.) Also, in someembodiments, by way of example, the disclosed systems and methods can beimplemented without a back channel.

The client and server can use any of a number of protocols tocommunicate. For example, in an embodiment using a Java client, the Javaclient can be configured to communicate with the server using RMI. TheJava Remote Method Invocation (RMI) system allows an object running inone Java Virtual Machine (VM) to invoke methods on an object running inanother Java VM. RMI provides for remote communication between programswritten in the Java programming language. The C# client can for examplecommunicate with the server using SOAP, or Simple Object AccessProtocol, which defines the use of XML and HTTP to access services,objects, and servers in a platform-independent manner or a similar aprotocol. The protocol used should preferably be able to handlemultiple, arbitrarily sized binary attachments inline.

Illustrative displays of user interfaces that facilitate collaborationare shown in FIGS. 3A-3G. The illustrative displays can include one ormore check boxes, one or more response boxes, one or more radio buttons,one or more pull-down menus, one or more icons, and/or one or more othervisual objects to facilitate collaboration. Those of ordinary skill inthe art will understand that the illustrative displays are to beinterpreted in an exemplary manner and that displays different thanthose shown and described herein can be used within the scope of thepresent disclosure. For example, features of the illustrative displayscan be combined, separated, interchanged, and/or rearranged to generateother displays.

The illustrative displays can be provided by a server, a client, or acombination thereof (e.g., resident collaboration software applicationimplemented on a client) The illustrative displays are described in thecontext of interactions (e.g., requests and responses) between client120 and server 140 in system 100.

FIG. 3A shows an exemplary login window 300 that provides access tosystem 100. As shown in FIG. 3A, the login window 300 includes query box302 for providing a username and query boxes 304-308 for providingauthorization information (e.g., password, domain name, and server name)for accessing system 100. The login window 300 also includes data entrybutton 309 for submitting the username and authorization information toserver 140.

FIGS. 3B and 3C show an exemplary welcome window 310 that providesaccess to places and friends. As shown in FIGS. 3B and 3C, the welcomewindow 310 includes place icon 311 and friend icon 312. As shown in FIG.3B, based on a selection of the place icon 311, the welcome window 310provides icons 314 for selecting among one or more pre-existing places.The places 314 can be organized into categories, e.g., the categoriesall places, my places, recently visited places, and new places. As shownin FIG. 3C, based on a selection of the friend icon 312, the welcomewindow provides icons 317 for establishing chat sessions with friends.In some embodiments, selecting and/or otherwise designating friend icon317 can produce a display of at least some of the on-line status data230 associated with the corresponding friend. As shown in FIGS. 3B and3C, the welcome window 310 can also include icons 315, 316, 319 and 305for establishing a new place, establishing a new user group, adding afriend, and adding to user data.

FIG. 3D shows an exemplary place interface for a user of system 100. Asshown in FIG. 3D, the interface 320 includes primary window 322, severalsub-windows 324-330, pull-down menus 332, icons 334, and a tray 338.Sub-window 324 (otherwise referred to herein as the people window 324)is configured for displaying data identifying the participants in anactive place. For example, people window 324 shows a list of participantuser names. In some embodiments, such as the embodiment shown in FIG.3D, people window 324 is configured for displaying miniature screenshots or “thumbnails” 324 a of the place interfaces (and/or portionsthereof and/or other displays) or other local content of a client (e.g.,active window or desktop application). Sub-window 326 (otherwisereferred to herein as the things window 326) is configured fordisplaying data identifying the place data files 260 that are associatedwith the place as well as the user data files 248 that are associatedwith a user. For example, things window 326 displays a data filedirectory including public portion 326 a and private portion 326 b.Selecting a data file in things window 326 (by, e.g., double-clicking onthe file with a mouse) causes the data file to be presented insub-window 328 (otherwise referred to herein as content window 328). Thecontent window 328 can present content 328 a, tooolbars 328 b formodifying the content, and scrollbars 328 c for navigating the content.Sub-window 330 (otherwise referred to herein as the chat window 330)includes portions 330 a and 330 b. Portion 330 a is configured fordisplaying a chat transcript, and portion 330 b is configured forreceiving chat messages for transmission, e.g., to friends and/or toother users in a place. Chat window 330 also includes an icon 331 fordisplaying prior chat transcripts, e.g., chat transcripts generatedduring previous visits to a place.

With continuing reference to FIG. 3D, a control panel 390 can bedisplayed in adjacent or contiguous relationship with the content window328 based on receiving a request from a user to share content with otherusers. As shown in FIG. 3D, the control panel 390 can include a visualobject 392 identifying a quantity of users sharing (i.e., observing) thecontent presented in the content window 328, a control icon 394 forpassing and/or requesting control of (e.g., permission to edit and/orotherwise write to) the shared content, and a viewer reception statusbar 396 representing the quality of the connection between the userssharing content.

With continuing reference to FIG. 3D, the pull-down menus 332 (labeled“File, Edit, View, Share, Tools, Window, Help”) allow a participant of aplace to access, view, and otherwise manipulate data files. The icons334 allow a participant of a place to select among the people, things,content, and chat windows 324, 326, 328, and 330 for display within theprimary window 322. For example, based on a selection of one of theicons, the sub-window corresponding only to that icon is displayed. Alsofor example, based on a consecutive selection of multiple icons, thedisplay of the place interface can be “gracefully” (i.e., gradually)escalated, e.g., from a single sub-window to two or more sub-windows,facilitating synchronous and/or asynchronous interactions among users ina place. As shown in FIG. 3D, the tray 338 includes connection statusindicator 340 that provides data representative of the connectionbetween client 120 and server 140. The connection status indicator 340can include a bar graph or other type of statistical indicator thatindicates one or more of a ping time, a back channel response time, aconnection quality and/or other connection statistics. In someembodiments, tray 338 can include icons or other visual objects forloading or otherwise accessing applications (e.g., icons for accessing aword processing application, a spreadsheet application, etc.) in aplace.

If desired, window 328 can be configured to also provide personalorganization tools that display information supporting the currentplace. For example, as show in FIG. 3F, a list of documents to bereviewed can be displayed, a list of upcoming meetings and/or help toolscan be displayed. This functionality can for example be displayed whenwindow 328 is not being used for content sharing.

A meeting window displayed in the exemplary place interface 320 of FIG.3D can display a meeting name identifier, meeting status indicator thatrepresents the current status of the meeting (e.g., just started,paused, ending in five minutes, etc.), a meeting icon for controllingthe status of the meeting (e.g., starting, pausing, resuming, and/orending the meeting), a presenter identifier that identifies the useridentifier of the meeting presenter, and a podium that includes aminiature screen shot or “thumbnail” of the content being shared by themeeting presenter.

FIG. 3E shows an exemplary meeting invitation window 370 for display inthe exemplary place interface 320 of FIG. 3D. As shown in FIG. 3E, theexemplary meeting invitation window 370 includes meeting icon 371 and anagenda icon 374. Based on a selection of the meeting icon 371, theinvitation window 370 provides one or more visual objects for schedulinga meeting in a place among users of system 100. For example, the meetinginvitation window 370 includes response boxes 372 for providing a name,a description, a start time, and a duration of a meeting to bescheduled, response boxes 374 for providing data related to anaccompanying telephone conference call (e.g., a telephone number of theconference call and a password or passcode for accessing the conferencecall, etc.), a recurrence icon 376 for establishing the recurrence ofthe meeting (e.g., one time, daily, weekly, etc.), participant and guesticons 378 for identifying the users of system 100 to be invited to themeeting, an email icon 380 for transmitting email invitations to theinvited users, a scheduling icon 382 for scheduling the transmission ofthe email invitations, and an options icon 384 for selecting one or moreadditional meeting options (e.g., options for archiving the meeting,emailing a meeting summary to the invited users, etc.).

By selecting agenda 379, further options or features related the meetingcan be configured. For example, with reference to FIG. 3G, Agenda window373 is displayed. Window 373 provides a list of Agenda items 380 for themeeting. Each item 380 provides a title of the agenda item, a presenter,a duration, and a notes section. Agenda items 380 are user-configurable(e.g., to select a presenter for an agenda item).

In one illustrative operation and with reference to FIG. 1A, thesoftware application program executing within memory 118 of the client120 can detect a request 138 to access a place from the user 102 by, forexample, receiving an indication from the I/O subsystem 124 thatdetected a mouse click, a keyboard entry, and/or another input eventinitiated by the user 102 (e.g., an entry received with respect to thelogin window 300 of FIG. 3A). In reply to the request 138, the softwareapplication program 104 instructs the graphics subsystem 122, via theprocessor 114, to display one or more options for selection by the user102 and/or one or more requests for information from the user 102. Theuser 102 can then initiate another input event corresponding to, forexample, an entry or selection of a place identifier (e.g., a selectionreceived with respect to welcome window 310 of FIG. 3B). Similarsequences of input events and detections by the software applicationprogram 104 can enable the user 102 to specify one or more additionalparameters that define the request 138. The request 138 (and, moregenerally, other requests generated by client 120) and its associatedparameters selected by the user 102 can be maintained in the memory 118of the client 120 prior to transmission to the server 140 via thenetwork 110. The software application program 104 can apply one or morerules to the request 138 to reduce the occurrence of erroneous requests.One or more of these rules can be contained in memory 118. Alternativelyand/or in combination, the software application program 104 can accessone of more of these rules from the databases 150 via the network 110.Software application program 104 can apply one or more data validationrules to the request 138 to determine the validity of the parametersassociated with the request and notify the user 102 of errors.

With continuing reference to FIG. 1A, the software application program104 can instruct the network connection process 130 of the client 120 totransmit the parameters associated with the request 138 selected by theuser 102 to a calculation process or another software process associatedwith the software application program 108 executing on the server 140by, for example, encoding, encrypting, and/or compressing the selectedrequest 138 into a stream of data packets that can be transmittedbetween the networking subsystems 128 of the digital data processingdevices 120 and 140. The network connection process 132 executing on theserver 140 can receive, decompress, decrypt, and/or decode theinformation contained in the data packets and can store such elements ina memory accessible to the software application program 108. Thesoftware application program 108 can process the request 138 by, forexample, applying one or more place rules 148 to the request 138.

FIG. 4 schematically illustrates an example of steps involved in anembodiment of a method for establishing a new place.

As for example shown in FIG. 4, a request from a user (e.g., user 102 incommunication with client 120) for a user account is received at aserver (e.g., server 140) in system 100 (410 in FIG. 4). Based onreceiving the request, server 140 (e.g., a software application programresiding on server 140) prompts, queries, and/or otherwise requestsclient 120 to provide the login information (e.g., the user identifierand authorization information) to be associated with the user accountand used to restrict subsequent access to the account (420 in FIG. 4).Usually, based on receiving the request, the server 140 establishes asecure connection (e.g., a virtual private network (VPN) connectionand/or another type of secure connection known to those of ordinaryskill in the art) with the client 120 to inhibit and/or preventinterception of the login information by third parties. In someembodiments, server 140 prompts, queries, and/or otherwise requestsclient 120 to provide additional information for association with theuser account, e.g., the contact information described with respect touser data 210 in FIG. 2.

With continuing reference to FIG. 4, server 140 receives the logininformation and, in some embodiments, the contact information, andstores that information in user data 210 (430 in FIG. 4). Based onreceiving a request for establishing a new place (440 in FIG. 4), server140 queries, prompts, and/or otherwise requests client 120 to provide aplace identifier for and, in some embodiments, a description of the newcollaboration place (450 in FIG. 4). For example, server 140 can promptclient 120 based on instructing the graphics subsystem 122 of client 120to present the welcome window 310 of FIG. 3B on display device 126.Server 140 can then request that client 120 identify the authorizedparticipants of the new place (460 in FIG. 4). Usually, server 140provides the user identifiers 215 for the users of system 100 to client120, and requests that client 120 select and/or otherwise designate oneor more of those user identifiers to authorize access to the new place.Additionally, in some embodiments, server 140 requests client 120 toassociate one or more data files with the place (e.g., one or more datafiles residing on local memory) (470 in FIG. 4). As described herein, insome embodiments, such data files can be associated with the place basedon the dragging-and-dropping those data files (or representationsthereof, such as icons) into the place interface by client 120. Server140 establishes the new place based on (i) uploading the data files tobe associated with the new place, (ii) associating the place identifierof the new place with the description, the selected and/or otherwisedesignated user identifiers of the authorized participants, and theuploaded data files, and (iii) updating user data 210 and place data 250to include data for the new place (480 in FIG. 4).

As previously indicated, in some embodiments, the originator of a place,such as client 120 in the context of FIG. 4, can select and/or otherwisedetermine the default features of the place interface. For example, inone such embodiment, server 140 can query, prompt, and/or otherwiserequest client 120 to select one or more default features. Alternativelyand/or in combination, in some embodiments, server 140 can provide oneor more groupings of default features to client 120 for selection. Eachgrouping can be associated with a field of use (e.g., business,engineering, humanities, legal, medical, scientific, etc.) and a trayincluding one or more predetermined applications that are relevant tothat field of use (e.g., a spreadsheet application for the businessfield of use, a whiteboard application for the engineering field of use,etc.). Based on receiving a selection of a grouping, server 140 canprovide a corresponding place interface to client 120.

FIGS. 5A-5C schematically illustrate an example of steps involved in anembodiment of a method for providing access to a previously establishedplace.

As shown in FIG. 5A, a request from user 102 ₁ interacting with client120(1) for accessing system 100 is received at server 140 in system 100(510 in FIG. 5A). Based on receiving the request, server 140 prompts,queries, and/or otherwise requests client 120(1) to provide logininformation associated with a user account (515 in FIG. 5A). Forexample, server 140 can prompt client 120(1) for the login informationbased on providing the login window 300 shown in FIG. 3A forpresentation on the display device 126 of the client 120. Usually, basedon receiving the request, the server 140 establishes a secure connectionwith the client 120(1) to inhibit and/or prevent interception by thirdparties of the login information and/or other data transmitted betweenclient 120(1) and server 140, such as, but not limited to, dataexchanged therebetween while the user is logged into a place.

With continuing reference to FIG. 5A, server 140 authenticates client120(1) based on receiving the login information (520 in FIG. 5A).Usually, server 140 authenticates client 120(1) based on querying theone or more databases 150, e.g., user data 210, to determine whetherthey include data corresponding to the login information. Based on notfinding data corresponding to the login information, server 140 deniesaccess to client 120(1) and, in some embodiments, provides an errormessage to client 120(1) and/or returns to 515 in FIG. 5A.

Based on finding data corresponding to the login information, server 140authenticates user 102 ₁ (i.e., client 120(1)) and queries databases150, e.g., user place data 220, to find user place identifiers 225associated with the user identifier 215 of user 102 ₁ (525 in FIG. 5A).In some embodiments, server 140 queries databases 150 to find other dataassociated with the user identifier 215, such as friend identifiers inuser friend data 245. Subsequently, server 140 prompts, queries, and/orotherwise requests client 120(1) to select among the user placeidentifiers 225 associated with the user identifier 215 (530 in FIG.5A). For example, in one embodiment, server 140 provides the user placeidentifiers 225 for selection based on instructing the graphicssubsystem 122 of client 120(1) to present the welcome window 310 ondisplay device 126. Subsequently, server 140 receives a selection ofplace identifier 225 from client 120(1) (535 in FIG. 5A) and queriesdatabases 150, e.g., place data 250, to find data associated with theselected place identifier 225, e.g., to find place data files 260, placeinterface data files 265, place log files 275, and place participantidentifiers 270 associated with the selected place identifier 225 (540in FIG. 5A).

Generally, client 120(1) and or server 140 can execute one or moresoftware application programs 104 and/or 108 that provide thefunctionality of a place interface. In some embodiments, the placeinterface programs reside exclusively on server 140 and are accessedremotely by client 120(1), and server 140 can customize the placeinterface for client 120(1) based on user skin data 235. Preferably,however, client 120(1) downloads the interface programs (e.g., based onan initial access to a place) and caches and/or otherwise stores theplace interface programs in local memory. Client 120(1) can customizeone or more features of the interface (e.g., the features previouslydescribed herein with respect to user skin data 235) and can cache orotherwise store data based on the customized features in local memory.For clarity, the place identifier 225 selected by user 102 ₁ at 535 inFIG. 5A is hereinafter referred to as the user 102 ₁ place identifier.

Regardless of whether the place interface programs reside on client120(1) and/or server 140, server 140 provides the data associated withthe user 102 ₁ place identifier (e.g., the data identified at 540 inFIG. 5A) to client 120(1) for presentation in the corresponding placeinterface (545 in FIG. 5A). In some embodiments, the data associatedwith the user 102 ₁ place identifier are displayed in place interfacessimilar to the exemplary place interface 320 shown in FIG. 3D. Usually,server 140 provides the data to client 120(1), and client 120(1) (e.g.,place interface program(s) 104 executing thereon) formats the receiveddata and presents the formatted data in the displays and sub-displays ofthe place interface. In some embodiments, however, server 140 (e.g.,place interface program(s) 108 executing thereon) formats the data andprovides to client 120 the formatted data and instructions fordisplaying the formatted data in displays and sub-displays of the place.

Subsequently, server 140 associates the IP or other network address ofclient 120(1) with the user identifier 215 of user 102 ₁ (550 in FIG.5B) and updates user data 210 and place data 250 (e.g., on-line statusdata 230 and place participant identifiers 270) to indicate that user102 ₁ is on-line in the place corresponding to the user 102 ₁ placeidentifier (555 in FIG. 5B). As further described herein, such anassociation facilitates administration of the place. Of course, based onreceiving an indication that the connection with client 120(1) isterminated (e.g., based on receiving an indication that client 120(1)has logged out of the place and/or system 100), server 140 updateson-line status data 230 and place participant identifiers 270 toindicate that user 102 ₁ is not on-line in the place corresponding tothe user 102 ₁ place identifier.

One or more additional participants can enter the place corresponding tothe user 102 ₁ place identifier based on features similar to thosepreviously described herein with respect to 510-535 in FIG. 5A. Forexample, based on receiving a selection of the user 102 ₁ placeidentifier from another user (i.e., another user authorized to accessthe place associated with that place identifier), e.g., user 102 _(M)interacting with a client 120(M) (560 in FIG. 5B), server 140 queriesdatabases 150, e.g., place data 250, to find place data files 260, placeinterface data files 265, place log files 275, and place participantidentifiers 270 associated with the user 102 ₁ place identifier (565 inFIG. 5B), at least some of which data may have been updated after theentrance of user 102 ₁ into the place (e.g., circa 555 in FIG. 5B).Server 140 then provides the place data 250 associated with the user 102₁ place identifier to client 120(M) for presentation in thecorresponding place interface (570 in FIG. 5B), associates the IP orother network address of client 120(M) with the user identifier of user102 _(M) (575 in FIG. 5B), and updates user data 210 and place data 250,e.g., on-line status data 230 and place participant identifiers 270, toindicate that user 102 _(M) is on-line in the place (580 in FIG. 5B).

With reference to FIG. 5C, server 140 also provides the thusly updatedplace data 250, e.g., the updated place participant identifiers 270, toclient 120(1) and 120(M) for presentation in the place interface,thereby notifying user 102 ₁ that user 102 _(M) is on-line in the place(585 in FIG. 5C). Alternatively and/or in combination, in someembodiments, server 140 pushes to and/or client 120(1) generates a userlogin notification message for presentation in the place interface ofclient 120(1). The message can be presented in a temporary display orwindow that is superimposed over a portion of the place interface and/oran active window of client 120(1). In some of such embodiments, server140 pushes to and/or client 120(1) generates such a message based ondetecting a login of a friend in friend data 245, regardless of whetherthe friend has entered an active place. Additionally, server 140 forms anetwork connection between clients 120(1) and 120(M), thereby providingclients 120(1) and 120(M) with access to the place corresponding to theuser 102 ₁ place identifier (590 in FIG. 5C). Preferably, server 140forms the network connection through itself, so that server 140 canmediate data exchange between and respond to requests from clients120(1) and 120(M).

As previously indicated, the client-server infrastructure of thedisclosed systems and methods supports a variety of asynchronous andsynchronous collaboration activities in a place. Preferably, in thedisclosed client-server architecture, each client can open at least twosockets to one or more servers administering the place. These socketsare referred to herein as the front channel and the back channel. Thefront channel supports request- and response-type interactions, e.g.,interactions in which a client transmits a request to a server, and theserver transmits a response to the client in reply thereto. In contrast,the back channel supports push-type interactions, e.g., interactions inwhich a server pushes or otherwise transmits unsolicited data to aclient. Communications on the front and back channels can be implementedusing protocols known to those of ordinary skill in the art, such as,but not limited to, simple object access protocol (SOAP) or SOAP-likeprotocols.

FIG. 6 schematically illustrates exemplary collaboration activities thatcan be performed in a place. As will be understood by those of ordinaryskill in the art, the disclosed systems and methods are not limited tothe types and/or the organization of collaboration activities shown inFIG. 6 and can be implemented to support additional and/or differenttypes and/or organizations of collaboration activities than those shownin FIG. 6.

As shown in FIG. 6, the exemplary collaboration activities include oneor more single-user perspective activities and one or more multi-userperspective activities. Single-user perspective activities includeactivities that can be performed by any user in a place, regardless ofwhether one or more other users are in the place. Some single-userperspective activities include establishing a new place, associating oneor more additional users with the place, gracefully escalating the placeinterface, associating one or more data files with the place and/or witha user office, viewing and/or editing place data files and/or user datafiles, and scheduling a meeting among users of system 100. Multi-userperspective activities include activities that are useful forcollaboration between two or more users in a place. Some multi-userperspective activities include detecting activities of other users inthe place, instantly meeting with other users in the place, pollingother users in a place, chatting with other users in the place, emailingother users in the place, sharing content with other users in the place,and establishing a voice conversation with other users in the place.Advantageously, the disclosed client-server infrastructure supportsseamless navigation among these different types of asynchronous andsynchronous activities in the place. Features of some of theseactivities will now be described.

In the following description, users and/or clients are said to be “in aplace.” Such terminology should be understood as a shorthand forreferences to users and/or clients who are logged into and/or otherwiseaccessing a place.

A user in a place can establish a new place based on the schemespreviously described herein, e.g., features 440-480 of FIG. 4.

The originator of a place (e.g., client 120 in the context of FIG. 4)can identify and/or otherwise designate those users authorized to accessthe place. Additionally, in some embodiments, those users authorized toaccess the place can themselves authorize other users to access theplace. In some of such embodiments, an authorized user of a place canassociate the user identifiers and/or other indicia of additional userswith the place via the place interface. For example, in one suchembodiment, the user can select and/or otherwise designate those useridentifiers based on selections from one or more of the pull-down menus332 in the exemplary place interface 320 shown in FIG. 3D. In someembodiments, based on receiving a selection of the user identifier,server 140 determines whether the corresponding user is on-line (e.g.,based on querying on-line status data 230), transmits an invitation toenter the place to the client 120 of the on-line user, and forms aconnection to the client 120 based on receiving an acceptance of theinvitation, thereby providing access to the place to the invited user.

In some embodiments, the disclosed systems and methods provide fordifferent categories of user membership in a place. Usually, theoriginator and/or an authorized user of a place will grant so-calledfull membership in the place to other users. The originator and/or theauthorized user can, however, grant limited memberships to other users,such as, but not limited to, time- or event-limited memberships.

In some of such embodiments, different types of membership can begranted to users who are members of a firm based on their positionsand/or responsibilities within the firm. For example, members who areresponsible for ensuring compliance with statutory and/or regulatoryschemes can be granted a first type of membership, while members who arenot so responsible can be granted a second type of membership.Additional features of ensuring compliance with statutory and/orregulatory schemes are described in U.S. patent application Ser. No.09/590,099, the contents of which application are expressly incorporatedby reference herein in their entirety.

A limited membership in a place can be understood to be a “guest pass”to the place. In some embodiments, one or more privileges within a placeare restricted to users based on their corresponding membershipcategories. For example, privileges to edit one or more of the datafiles 260 of the place can be restricted to users having fullmembership, while privileges to view one or more of those data files canbe available to all users, regardless of their membership categories.Also for example, the features of the place interface provided to userscan be dependent on the corresponding levels of user membership. Forexample, place interfaces supporting all types of interactions can beprovided to users with full membership, while place interfaces thatsupport a subset of interactions can be provided to users with limitedmembership. Also for example, a server in system 100 can support awebsite (e.g., an Internet website) that can be accessed by guests to aplace, so that guests interacting on clients 120 without softwareapplication programs 104 configured for supporting the place interfacecan experience at least some features of the place (e.g., instantmeetings). Generally, server 140 can administer and/or otherwiserestrict user access to and user privileges within places based oncorresponding membership categories based on schemes known to those ofordinary skill in the art.

One feature that enhances the synchronous-asynchronous collaborationsystems and methods involves techniques for graceful escalation within acollaborative object with which users interacting as part of theircollaboration. The main user-interface window of a client is for exampledivided into a number of sections including, for example, a chat panel,content area, people panel, and things panel. The content area containsa list of collaboration objects, artifacts from previous collaborationsessions, documents, folders, etc. These object or artifacts can be theartifacts or objects remaining from previous instantiations of acollaboration place as well as the new objects or artifacts that areintroduced in the current instantiation of the collaboration place. Asused herein, the term artifacts can be understood to include informationthat results from one or more user activities in a collaboration placeand that can be stored for later retrieval.

One of the ways in which a collaboration place can be initiated is basedon Instant Messaging (IM). When an IM session is initiated, just thechat panel is shown on the initiating client. Once a message is entered,the message is sent to the server and passed on to the receiving client.The receiving client pops up a normal-looking IM window, displays themessage, and then the two participants can talk back and forth normally.

At any point, if either of the participants adds a new content item tothe collaboration object, that fact will be shown to the other client byrevealing that panel and dynamically resizing the controls in the screento display it. It can also highlight any newly revealed areas byflashing the area, tray notification, sounds, etc. Either participantcan now easily use tools provided by the client to select and view thecontent item.

At any point, if either of the participants initiates screen sharing,the thumbnail image of the screen share is displayed next to their namein the other client. If the client selects the thumbnail, their windowwill again be dynamically reconfigured to show the shared screen intheir content area. They can be simultaneously chatting away, uploadingcontent, and sharing their screens.

If they invite other users to access the collaboration object, thepeople tab is automatically revealed and the window is reconfigured todisplay that panel as well.

The client implements these features by maintaining the state of anyconversation window internally and dynamically revealing additionalsections of the window as required. Each time one of these new sectionsis revealed, the window is reconfigured so they are all visible.

Thus, through the provision of views, users can experience, via thecomputer system, all the same things they would experience in areal-life conference or meeting room. For instance, contemporaneousdiscussion threads are analogous to side discussions in a real-lifemeeting. Attachments (documents etc.) can be brought to the “meeting”,or taken “home” from the meeting. Such a real life experience can beprovided through providing a conference chat, screen sharing ofapplications or documents, the ability to pass control of a document orapplication during collaboration (e.g., click access to a shared screento drive applications remotely such as by one user clicking to takecontrol of a shared document in an application to indicate his or herrevisions remotely during collaboration), tracking of synchronous andasynchronous activity, the presentation of state information aboutparticipants (e.g., variations in the color of an icon of a user to showa current characteristic of the user), “hot” areas such as the user'sicon that automatically display information about the user such as howlong idle, current activity, etc.

An important aspect of synchronous-asynchronous collaboration systemsand methods and related functionality in accordance with embodiments ofthe present invention is the storage (e.g., persistent storage) ofartifacts from all collaboration both synchronous and asynchronous andfor example the implementation of a designated container class as thebasis of the object model for incorporating those artifacts.

Also, in order to facilitate a graceful blend of synchronous andasynchronous collaboration, communications are structured and organizedin such a way that they can be accessed through either synchronous orasynchronous activity. This ability can provide synchronouscommunications with a location where they take place so thatparticipants might find the artifacts by accessing that location afterthe a synchronous communications session has taken place.

Typically, in known conventional technology, synchronous collaboration(e.g. IM) does not make any attempt to preserve artifacts. In otherwords, such known techniques do not recognize that there is anasynchronous aspect (an “afterlife”) of even the most immediate ofsynchronous objects. In addition, most IM clients can store a log ofmessage locally on a client machine, but they provide no capabilitiesfor centralized store of that data or storage of any of the otherartifacts—documents, voice, video, screen shares, etc. The fact that IMtypically does not provide persistent storage reflects the fact that itis a significant task to do so and that the value of doing so is notwidely recognized.

In addition, in known conventional systems, IM is inherentlypeer-to-peer and provides no context other than the individual users andtheir presence indication within the system. A drawback of such systemsis that the initiation of a collaborative session, therefore, must beginwith explanation of the context of the collaboration, may involvemanipulation of objects that reside in another system, and must end withmutual agreement on how to preserve the result of the collaboration.

In one example of an object-based implementation of the systems andmethods of the present invention, the object model relies upon atop-level container class, and every object has a “collaborationdesignation.” The “collaboration designation” is inherited by allartifacts of any collaboration activity, whether synchronous orasynchronous, and makes it possible, for example, to return to any ofthem for further collaboration and continued activity. This techniquehas several implications for the object model for implementing thecollaboration software. One implication is that not just obvious meetingartifacts (for example, meeting minutes) but, in fact, the full range ofall possible objects (including, for instance, all kinds of ordinarydocuments) are recognized as being characterized by a “collaborationdesignation.”

Such an architecture can provide an extensible framework that makes iteasy to build applications that support multiple, simultaneousparticipants manipulating a variety of different object types. Theframework also supports retrofitting existing applications (e.g., emailand transaction-based business applications) that may initiate abusiness process involving synchronous and asynchronous collaboration(together or separately) or that may be used to manipulate the objectsof collaboration (e.g., through the use of locks).

Element objects have certain properties, inherited by the next level ofobject sub-classes. As indicated above, these properties include atleast a name or “collaboration designation”. Depending on theembodiment, the designation may relate to a specific project, a specificdeliverable, other actions or people related to a team, meetings,meeting-related activity, etc., or some combination of these, or none ofthem. Further, within this illustrative structure, for example, theapplication can be implemented such that the “collaboration designation”could be said to relate to a “theme,” “topic,” “project,” etc. However,it is not a prerequisite for the operability of the system that anytheme, topic, project, etc., be identified; the system can be functionaljust as long as a unique “collaboration designation” exists. Virtuallyany naming convention that is suggestive of uniquely identifiableobjects suffices.

Instances of the container class can be implemented to provide visualcues that enable participants to understand the context of thecollaborative business process as well as the participants—includingthose participants currently engaged in a collaboration place as well asthose who may be invited to join a collaboration place in order tofacilitate the business process that is the subject of the place.

The name and other possible properties are inherited by a child class ofcontent objects, such as

-   -   meeting invitations    -   agendas    -   notes    -   attachments    -   minutes, including:        -   written        -   audio        -   video        -   contemporaneous discussion threads

The properties of the content objects may be further inherited by theirown child classes.

Permissions can be a configurable characteristic that can be importantin certain applications. Permissions can for example be attributes ofthe top-level container object or of individual components.

When using object based implementations, all GUI initiated interactionscan for example be managed by methods of the objects. Of particularinterest can be the methods that allow for the display and editing ofdifferent types of content objects simultaneously by multiple users.

While the typical paradigm of the IM systems in conventional systems ispresence indicator of the individuals on your contacts or friends list;a novel paradigm in accordance with some embodiments of the presentinvention is presence indicators in the collaboration container (e.g.“place awareness”). Therefore, while existing technology can allow auser to initiate an IM chat session with another individual, the presentexemplary technique allows a user to initiate a collaborative businessprocess within the context of a collaborative container involving zeroor more participants who may already be in a synchronous collaborationsession. In addition, the simple fact that a user entered thecollaboration container may trigger other individuals who subscribe to a“buddy list” including that container to join the user—through directinspection of the space, “peripheral” vision sensing a change to thespace, or event-based notification of an invitation to join the space.The artifacts that the user leaves behind in the collaboration space,can be immediately available to other current and future participants,assuming that the user granted appropriate access to those participantseither individually or based on their roles.

Further examples and illustrations that primarily relate to the gracefulescalation aspect of the systems and methods of embodiments of thepresent invention are provided herein as follows. These examples andillustrations should be understood to be implemented in accordance withthe above discussion as appropriate.

As discussed above, collaboration can be enhanced through a softwareapplication and related data that provide integrated tools for livecollaboration. The software application can be configured to augment awindow or collaboration space of network users on a gradual basis. Theseescalating enhancements in functionality can be initiated in a number ofdifferent ways. One way is to allow a user to drag and drop desiredcontent into a current user space to automatically “escalate” the spaceto an enhanced state. If desired, the enhancement can be configuredautomatically to match the current state of collaboration such as bymatching the enhancements to the type of document that triggered the“escalation.”

The initial nucleus of collaboration can be a functional item,application, or other software item that is available to a user. Forexample, the nucleus can be a network collaboration tray, a desktopapplication, an icon (e.g., in the task bar), or other software pointwhere a user can, for example, drag in a co-worker, a document, anapplication, or other collaboration related item into the starting pointor other designated point to escalate that space into a needed state ofcollaboration. The shape and display of the initial space and subsequentspaces can automatically change or increase in size and content insynchronization with the escalation. An important feature is that theuser is provided with the ability to seamlessly move from working on aproject individually or working on a project collaboratively in asynchronous object to an enhanced collaboration object. This caneliminate procedural hurdles and steps that can exist in conventionaltechnology.

Escalation may include a repository, document editors, document viewersor players, time and schedule management, network resources, enterpriseresources, e-mail, browsers, conferencing, desktop applications, officetools, or other applications. Participants may be users of an enterpriseplatform, an Internet platform, or other network platform.

Escalation can be trigged by allowing a user to drag and drop an iteminto a particular space to commence collaboration or to enhance anexisting collaboration space. Other techniques may include a menu optionthat a user can select to identify collaboration targets.

Automatically triggered escalation may be based on the attributes ofcollaboration participants or other attributes such as the time, theattributes of a current document, a task assignment, a link within acurrent document to a particular application, etc.

In one embodiment, a resident application is implemented on a clientcomputer platform that is configured to integrate a plurality ofdifferent collaboration tools (e.g., synchronous, asynchronous) whereinthe tools can be available to user on demand during collaboration usingone of the tools to provide related collaboration on the same subjectsor objects (e.g., seamless integration). If desired, layers of tools arealways available but only triggered in response to a natural action of auser indicating collaboration (e.g., options from layers are not merelyvisible, but are automatically available when the interaction focuses ona different type of interaction).

FIG. 12A shows an illustrative sequence of gradual collaborationactivity. A network-connected user can have access to a “live tray” ontheir desktop. The tray can be a portal to live or asynchronouscollaborative features. In this example, the tray includes a list ofusers such as a list of registered users of the collaborative software.

A network user can initiate a chat session with one of the users listedin the tray (e.g., by clicking on that user). During the initiated chatsession, one of the participants can drag a document from their desktopinto the chat session. In response, the collaboration object is enhancedto include a view of the document and related options. Chat participantsmay desire to add video to the real-time collaborative object to furtherenhance their collaboration activities. Subsequently, a videoconferenceor other video may be added.

FIG. 12B shows an illustrative sequence of gradual collaborationactivity involving a different starting point for the collaborationactivity. In this case, the starting point of the collaboration space isa user's word processor application. To initiate collaboration, the userdrags an icon or other identifier for an individual into the applicationspace of the word processor. In response, a collaborative space for livecollaboration is created that includes a chat session and a view of adocument in the word processor application. A further level ofescalation can be to provide a repository for the collaborative spacethat is triggered automatically or manually by the participants of thecollaborative space. An even further level of escalation is to add asection for enterprise resources in the collaborative space. Theenterprise resources can for example allow the users to set theparameters for the broadcast of a document in the collaborative space.

FIG. 12C shows illustrative examples of different escalation techniques.For example, a chat session may be enhanced to include a graphicssoftware application or a graphics document when the participants of thechat session invite a graphic artist to join the chat session. Inanother example, a chat session may be enhanced to include projectcontent (e.g., a presentation) in a window when the participants of thechat session invite a point of contact for that project to join the chatsession. In a further example, a graphics editor may be automaticallyadded to a collaborative space when the participants of a chat sessionselect to add a word processing document that includes a graphicalobject to their collaborative space. In another example, chatparticipants may “drag-in” a software application into the collaborativespace (e.g., a document editor) to initiate collaborative work in thatapplication.

FIG. 12D shows a sequence involving template-based escalation. In thiscase, templates that for example are geared to specific tasks orindustries may be available for use by the participants of a chatsession. The templates allow users to move more quickly through theintermediate escalation steps. Templates may also be cumulatively linked(e.g., two saved templates can be linked to provide a cumulativetemplate combining the features of the two saved templates).

FIG. 12E shows an illustrative sequence of gradual collaborationactivity that is based on stored sessions. A list of storedcollaboration sessions may be made available to a network user. The usermay be allowed to select one of the sessions. In response, a sessionwindow may be displayed that includes a repository of session content.The repository can include stored session content or other content(e.g., documents, images, web pages, images, etc.) that were stored tobe part of that session and visible to clients in that session. When astored session's content is selected, the collaborative space can beautomatically recreated to include different aspects that existed inthat collaboration (e.g., windows for video, chat, documents, etc.).Escalation in this case is provided so that collaborative space that isrecreated automatically matches the stored session content. Otherfeatures shown in FIG. 12E include an area that identifies the list ofclients (users) currently present in the session (e.g., using nameidentifiers and icons) and includes thumbnails of applications orcontent next to clients that is available for sharing by those present.By clicking on a thumbnail, the contents of the thumbnail is shared withthe client that clicked on that thumbnail.

Two examples of applications of features of the systems and method ofthe present invention are provided herein as follows.

During a chat or instant message session, the participants decide toestablish a “meeting” or “collaboration”—to which additionalparticipants can be invited. A meeting scheduler can be added toaccommodate the planning and scheduling of the meeting.

A user involved in entering invoices into a system may find that he orshe is faced with a question that requires collaboration with someoneelse. Instead of exiting the application and using a separateapplication (e.g. IM, email, etc.) to commence collaboration, they canbegin collaboration directly from the interface they were using and thenthat application and its underlying information will be available to theother user in the course of the problem-solving session. In this case,the initiating user makes his screen available to the other person forviewing—“over his shoulder.” If desired, the initiating user may passcontrol of his screen (e.g., via a mouse, keyboard, etc.) to the otherperson. In another embodiment, the initiating user may allowco-operation of the application (e.g., co-editing).

In another illustrative embodiment, the current desktop document oractivity of a network user may be visible (e.g., a thumbnail view nextto a user icon) to other network users. With this information, a networkuser can choose to join another user to participate in their work. As aresult, a collaborative space for their joint work based on the documentor desktop of the users may be created.

FIG. 12F is illustrative of the range of escalation that can beavailable to users. FIG. 12F shows an illustrative chart that containexamples of type of nodes or activates from which escalation orde-escalation can be implemented to occur. An objective would be toprovide a seamless transition for users to match their currentcollaboration needs as the substances of their collaboration whethersynchronous or asynchronous evolves from beginning to end. In the chartof FIG. 12F, such mobility is exemplified. In the figure, private refersto a collaboration place where two people chat and/or share content.“Public” refers to a collaboration place where three or more people chatand/or share content. “Outsider” refers to an external user, such as onewho does not have a login or identity within the collaboration system.The transition can for example be triggered manually, but is preferablyimplemented automatically in response to an action by a user related toa type of collaboration that automatically implements or withdrawsaccessibility to a new display interface for that particular type ofcollaboration.

As such an aspect of some embodiments of a collaboration place andrelated features can include implementing an executable software onclient computers that displays an interface for a first collaborationtool that is network-accessed by others to provide the desired type ofcollaboration. The executable software includes a plurality ofcollaboration tools that are integrated together. The softwarepreferably makes the other collaboration tools available through sensingthe type of collaboration activity sought by the users of a currentlydisplayed collaboration tool. As such, a number of different tools canbe available for use but are triggered to be displayed based for exampleon a user taking an action or contributing an object that concerns oneof the other collaboration tools to types of collaboration not yetdisplayed. If desired, such functionality can be implemented in adifferent ways by for example, using separate executable for each tool.

A place interface usually includes a primary display and one or moresecondary or sub-displays within the primary display, in which eachsub-display supports a different type of collaboration activity or adifferent feature of a place. In some embodiments, an end user 102 cangracefully escalate the primary display of the place interface so as toinclude a single sub-display, two sub-displays, or more than twosub-displays, i.e., so as to support one type of collaboration activityor place feature, or two or more types of collaboration activities orplace features. For example, in one such embodiment, the icons 334 inthe exemplary place interface 320 shown in FIG. 3D allow a user toselect among the people, things, content, and chat windows 324, 326,328, and 330 for display within the primary window 322. Based on aselection of one of the icons, the sub-window corresponding only to thaticon is displayed; based on a consecutive selection of multiple icons,the display of the place interface can be gradually escalated, e.g.,from a single sub-window to two or more sub-windows. Additional featuresof graceful escalation schemes are disclosed in U.S. Patent ApplicationSer. No. 60/607,388, the contents of which application are expresslyincorporated by reference herein in their entirety.

One or more data files can be associated with a place (or, morespecifically, a place identifier 255). Generally, data files areassociated with the place based on receiving requests from one or moreclients 120 logged into the place. For example, a request from a client120 for transmitting a data file from a local memory into a place isreceived at server 140. Such a request can be generated during aninitial establishment of the place (e.g., at 470 in FIG. 4) and/or at alater time (e.g., during an initial or subsequent visit to the place).In some embodiments, the request can be generated based on a selectionfrom a pull-down menu 332 in the exemplary place interface 320 of FIG.3D. Based on receiving the request, server 140 uploads the data filefrom the local memory of the client 120 based on file transfer protocol(FTP) and/or other data file transmission protocols known to those ofordinary skill in the art, updates the place data files 260 associatedwith the place identifier 255 for the place to include the uploaded datafile, and provides the updated place data files 260 to client 120 andother clients 120 in the place for presentation in the correspondingplace interfaces (e.g., for presentation in the data file directory inthings window 326 of FIG. 3D).

Preferably, data files can also be associated with the place based ondetecting dragging-and-dropping actions of the clients 120 in the place.In some embodiments, client 120 and/or server 140 can detect adragging-and-dropping of an icon for a data file (e.g., by an inputdevice of client 120, such as a mouse) from outside and into the placeinterface for a place (e.g., from a desktop of client 120 and/or from aninterface for a different place). Based on detecting the dragging anddropping of the icon, server 140 uploads the data file associated withthe icon from the local memory of the client 120, updates the place datafiles 260, and provides the updated place data files 260 to clients 120for presentation in the corresponding place interfaces.

In some embodiments, client 120 and/or server 140 are configured foridentifying the display (e.g., the secondary or sub-display) of theplace interface into which a dragged icon is dropped. For example, inone such embodiment, client 120 and/or server 140 can determine whetherthe icon is dropped into the chat window 330, the content window 328,the people window 324, or the things window 326 of the exemplary placeinterface 320 shown in FIG. 3D.

In some of such embodiments, the window into which the icon was droppedcan be used to determine the presentation of the data file in the placeinterface after uploading. For example, in one such embodiment, based ondetermining that an icon was dropped in the content window 328, server140 can provide the corresponding uploaded data file for presentation inthe content window 328 and the updated place data files 260 forpresentation in the things window 326. Also, based on determining thatan icon was dropped in the content window 328, server 140 can add thecontent of the uploaded data file to a place data file 260 that iscurrently being viewed in the content window 328. For example, server140 can paste the content as a bitmap at the icon drop location. Alsofor example, in one such embodiment, based on determining that an iconwas dropped in a chat window 330, server 140 can provide (i) the updatedplace data files 260 for presentation in the things window 326 and (ii)a link to the corresponding uploaded data file in place data files 260for presentation in the chat window 330. The disclosed systems andmethods thus support dragging-and-dropping of data files from localmemory into a chat utility.

One or more data files can be associated with a user office and storedin user data files 248. In most embodiments, data files are associatedwith a user office based on detecting a dragging-and-dropping of an iconfor the data file from outside and into the office utility of a placeinterface, e.g., from local memory on client 120 and/or the publicportion of thing window 326 into the private portion 326 b of thingwindow 326. In some embodiments, data files are associated with a userbased on receiving a selection from a pull-down menu 332 in theexemplary place interface 320 shown in FIG. 3D. The data files 248 thatare associated with a user office are accessible to the user in eachplace which the user visits via the office utility in the correspondingplace interfaces. Since the user data files 248 are stored on databases150, they can be provided to the user regardless of the client 120 withwhich the user 102 interacts. Advantageously, therefore, the data filescan “follow” the user from client 120 to client 120 in network 110.

The previously described schemes for uploading data files into a placeand/or a user office from client 120 can be suitably modified based onschemes known to those of ordinary skill in the art for downloading datafiles from the place and/or the user office to client 120.

In some embodiments, the disclosed systems and methods provide aninteraction log utility that allows users to associate a data file withtwo or more places. Such linking can reduce data storage constraints onsystem 100. For example, in some of such embodiments, a user who desiresto access a data file in two different places can upload the data fileto one of the places, and then the uploaded data file can be associatedwith the other of the places via the interaction log utility. Theinteraction log utility can be accessed based on a request from client120, e.g., based on a selection from a pull-down menu 332 in theexemplary place interface 320 of FIG. 3D.

In some embodiments, a user in a place can view and/or edit one or moreof the place data files 260 and or the user data files 248 via a datafile utility that is provided in the place interface. An exemplaryembodiment of a data file utility will now be described with respect tothe content window 328 of the exemplary place interface 320 shown inFIG. 3D. The exemplary data file utility will be described with respectto viewing and editing a place data file 260.

As shown in FIG. 3D, the exemplary data file utility or content window328 is configured for presenting the content of one or more of the placedata files 260. User 102 interacting with client 120 and desiring toview place data file 260 can request to view the data file by selectingthe icon for the data file that appears in things window 326. In someembodiments, based on receiving the request from client 120, server 140transmits the place data file 260 to client 120, and client 120temporarily stores and/or otherwise caches the place data file 260 in alocal memory. The software application program(s) 104 configured formanipulating the data type of the place data file 260 and the placeinterface program(s) 104, 108 residing on client 120 and/or server 140cooperatively present the content 328 a of the place data file 260,toolbars 328 b for modifying the content, and scrollbars 328 c fornavigating the content in content window 328.

As will be understood by those of ordinary skill in the art, client 120may not necessarily include software application program 104 configuredfor manipulating the data type of the place data file 260 desired to beviewed. As such, in some embodiments, based on receiving a request fromclient 120, server 140 identifies and/or otherwise determines the datatype of the place data file 260 desired to be viewed and then prompts,queries, and/or otherwise requests client 120 to indicate whether client120 includes software application program(s) 104 that are configured formanipulating the identified data type. Based on receiving an affirmativeresponse from client 120, server 140 transmits the place data file 260to the client 120, and the place data file 260 is presented in contentviewer 328 based on the previously described schemes. Based on receivinga negative response from client 120, server 140 executes softwareapplication program(s) 108 configured for manipulating the identifieddata type, formats the place data file 260 for presentation, andtransmits the formatted data file to client 120 with instructions forpresenting the data file in content viewer 328.

Generally, client 120 can edit and/or otherwise modify the content 328 aof a data file that is presented in content viewer 328 based onmanipulating toolbars 328 b and/or scrollbars 328 c and/or based onother functionality supported by the software application program(s) 104and/or 108 that are configured for manipulating the data file (e.g.,based on input device functionality, such as keyboard or mousefunctionality, supported by the program(s) 104 and/or 108). Usually,server 140 detects changes to the content of a place data file 260 beingmodified via content viewer 328 and updates place data files 260 toinclude the changes based on schemes described herein and/or based onschemes known to those of ordinary skill in the art.

In some embodiments, a user can schedule a meeting in a place with otherusers of system 100 via a meeting invitation utility provided in theplace interface. An exemplary embodiment of a meeting invitation utilitywill now be described with respect to the meeting invitation window 370shown in FIG. 3E.

User 102 ₁ interacting with client 120(1) can schedule a meeting at apre-determined time with other users 102 _(M) in a place via the meetinginvitation utility. In some embodiments, user 102 ₁ can activate themeeting invitation utility based on a selection from a pull-down menu332 in the exemplary place interface 320 shown in FIG. 3D. Based onreceiving the selection, server 140 can provide the meeting invitationwindow 370 to client 120(1) for display in the corresponding placeinterface 320. User 102 ₁ can enter and/or otherwise provide meetingdata (e.g., meeting name, meeting start time, etc.) in the meetinginvitation window 370 and upload the meeting data to server 140. At orabout the meeting start time, server 140 performs feature 730 of FIG. 7and otherwise administers the meeting based on performing features740-780 of FIG. 7, which features are further described herein withrespect to FIG. 7. Server 140 continues to administer the meeting untila request to terminate the meeting is received (e.g., from one or moreof the users 102) and/or the meeting end time is reached.

In some embodiments, the disclosed systems and methods can be integratedwith conventional calendar and/or e-mail personal applications (such asMicrosoft Outlook®) so that users can synchronize and/or otherwiseupdate their personal calendars with scheduled meetings.

In some embodiments, the users in a place can detect the type and/ordegree of activity of other users in the place based on one or moreso-called peripheral vision schemes. For example, in one such scheme, auser can detect the activity of other users based on the user loginnotification messages described herein with respect to FIGS. 1B and5A-5C. Also, a user can detect the activity of other users based onminiature screen shots or “thumbnails” of the place interfaces ordisplay screens (or portions thereof) of the other users describedherein with respect to FIGS. 8A and 8B. (In some embodiments, athumbnail can also indicate the number of users currently viewing theshared display represented by the thumbnail and, based on a selection ofthe thumbnail by a user input device (e.g., a mouse), the identities ofthe users.) Further, a user can detect the activity of other users basedon the activity indicators previously described herein with respect toFIG. 1B.

In some embodiments, a first user desiring to learn the activity statusof a second user in a place can select and/or otherwise designate theuser identifier for the second user in the place interface, e.g.,welcome window 310 and/or people window 324. Based on receiving theselection, server 140 can provide the activity indicator (e.g., thepreviously described simple and/or the complex activity indicator)associated with the second user for presentation in the place interfaceof the first user. In some of such embodiments, a user in a place canmanually set one or more features of and/or otherwise disable theactivity indicator. For example, a user can set the simple and/orcomplex activity indicator to “busy” so as to discourage chat messagesfrom other users and/or can disable the simple or complex activityindicator to enhance privacy.

In some embodiments, the disclosed systems and methods can provideadditional information to the first user. For example, in some of suchembodiments, the disclosed systems and methods can provide one or moreof the following to the first user: data identifying all of the datafiles currently being viewed by each user in a place; data identifyingall of the data files that have been viewed during a time period by oneor more users in a place; data identifying all of the users who haveaccessed one or more data files during a time period; and dataidentifying data files accessed and edited by one or more users during atime period. In some embodiments, the provided data can include one ormore thumbnails (e.g., thumbnails of the data files currently beingviewed by users in a place) and/or one or more other types of real-timeviews.

In some embodiments, a user can initiate an instant meeting with otherusers in a place via an instant meeting utility provided in the place.FIG. 7 schematically illustrates an example of steps involved in anembodiment of a method for establishing an instant meeting in a place.

As shown in FIG. 7, a request from a user 102 ₁ interacting with client120(1) and desiring to establish an instant meeting in a place isreceived at server 140 in system 100 (710 in FIG. 1). In someembodiments, the request can be generated based on a selection from apull-down menu 332 in the exemplary place interface 320 shown in FIG.3D. For example, the request can be generated based on a selection ofthe “Instant Meeting” icon in the pull-down menu 332. Based on receivingthe request, server 140 prompts, queries, and/or otherwise requestsclient 120(1) to provide a meeting name for association with the instantmeeting (720 in FIG. 7). Based on receiving a meeting name, server 140transmits at least the meeting name and, preferably, a meeting statusindicator and a meeting presenter identifier to clients 120(1) and120(M) (i.e., all clients 120 currently entered and/or otherwise loggedinto the place) for display in the corresponding place interfaces (e.g.,meeting windows 350 in exemplary place interfaces 320) (730 in FIG. 7).

Usually, clients 120(1) and 120(M) participate in an instant meeting ina place via the place interface for the place. Alternatively, in someembodiments, based on receiving a request for an instant meeting fromclient 120(1), server 140 can provide one or more groupings of defaultmeeting features of the place interface for the instant meeting toclient 120(1) for selection. In some of such embodiments, each groupingis associated with a field of use (e.g., business, engineering,humanities, legal, medical, scientific, etc.) and one or more displaysand/or one or more trays that are relevant to that field of use, such astrays that include one or more pertinent applications (e.g., aspreadsheet application for the business field of use, a whiteboardapplication for the engineering field of use, etc.). In some of suchembodiments, each grouping is associated with a type of meeting (e.g.,reporting meetings; interpersonal meetings; working meetings; salesmeetings; informational meetings; training meetings, etc.) and caninclude one or more displays and/or one or more trays that are relevantto the meeting type. Additionally, one or more of groupings can bedeveloped and/or otherwise customized by client 120(1). Based onreceiving a selection of a grouping, server 140 can provide acorresponding place interface to clients 120(1) and 120(M) in the place.

Subsequently, user 102 ₁ or another user 102 _(M) in the place canrequest to be the meeting presenter (colloquially referred to herein as“request the podium”). Based on receiving the request (740 in FIG. 7),server 140 updates the meeting presenter identifier to include the useridentifier of user 102 ₁ and prompts, queries, or otherwise requestsclient 120(1) to determine whether to share content (750 in FIG. 7).Based on receiving an indication of content sharing, server 140 performsfeatures 830 and 840 of FIG. 8A further described herein and transmitsthe miniature screen shot or “thumbnail” of the shared content and theupdated meeting presenter identifier to clients 120(1) and 120(M) forpresentation in the corresponding place interfaces (760 in FIG. 7).Server 140 updates the meeting status indicator at intervals (e.g., toshow elapsed meeting time) (770 in FIG. 7) and administers requests forthe podium and other interactions between clients 120 based on theschemes described herein and schemes known to those of ordinary skill inthe art until receiving a request to terminate the meeting (780 in FIG.7).

In some embodiments, a user can initiate a poll of users in a place viaa poll utility provided in the place interface. Such a poll can be usedto evaluate and/or otherwise solicit user opinions. An exemplaryembodiment of a method for establishing a poll in a place will now bedescribed.

In the exemplary embodiment, a request from a user 102 ₁ interactingwith client 120(1) and desiring to take a poll of users in a place isreceived at server 140 in system 100. In some embodiments, the requestcan be generated based on a selection from a pull-down menu 332 in theexemplary place interface 320 shown in FIG. 3D. For example, the requestcan be generated based on a selection of a poll icon in the pull-downmenu 332. Based on receiving the request, server 140 prompts, queries,or otherwise requests client 120(1) to provide poll data. Generally,poll data includes data representing a populace to be polled, a durationof the poll, a poll query, and, in some embodiments, a poll anonymityindicator.

The populace to be polled can include one or more users of the place(or, more generally, one or more users of system 100). For example, thepopulace to be polled can include all users authorized to access theplace, all users currently logged into the place, and/or one or moreother groupings of one or more users. Also, the populace to be polledcan include one or more invitees to a meeting (e.g., a scheduled and/oran instant meeting). For example, the populace to be polled can includeall invitees to a meeting, all invitees currently in a meeting, and/orone or more other groupings of invitees.

The poll duration indicates either the time period over which responsesto the poll can be cast by the poll populace or the time at which thepoll will be closed and/or responses tallied. As such, the poll durationcan be described in terms of a predetermined quantity of time (e.g., tenminutes) and/or a pre-determined future time (e.g., Monday at 9 AM). Insome embodiments, the poll duration can be unspecified (e.g., at yourconvenience). In some of such embodiments, server 140 can query client120(1) at intervals (e.g., at periodic intervals and/or other types ofintervals determined by client 120(1)) whether to close and/or otherwisetally the poll.

The poll anonymity indicator represents the default degree of anonymityto be associated with poll responses from the poll populace. Usually,the poll anonymity indicator includes an anonymity type (e.g., anonymousor non-anonymous) and a fixed or variable setting. A fixed settingindicates that the anonymity type cannot be changed by poll respondents,while a variable setting indicates that the anonymity type can bechanged as desired by poll respondents. Some possible poll anonymityindicators include fixed anonymous, variable anonymous, variablenon-anonymous, and fixed non-anonymous. Other poll anonymity indicatorswill be apparent to those of ordinary skill in the art.

Based on receiving poll data, server 140 transmits the poll query andduration to the poll populace (e.g., clients 120(1) and 120(M)) forpresentation in the corresponding place interfaces. In most embodiments,the poll question is accompanied by response icons (e.g., yes/no/maybeicons) and/or response boxes (e.g., for providing user comments).

Based on receiving a response to the poll query from a respondent,server 140 determines whether the anonymity indicator setting can bechanged. Based on so determining, server 140 queries, prompts, and/orotherwise requests the respondent to determine the desired setting.

Server 140 stores responses to the poll from the poll populace in placelog files 275 and transmits data based on the responses (e.g., a tallyof yes/no/maybe responses and/or a summary of comments) to the initiatorof the poll, i.e., client 120(1), based on detecting the poll duration.Of course, if desired by the poll initiator, server 140 can transmitthat data to the entire poll populace. Server 140 transmits the databased on the responses consistent with the anonymity specified by thepoll anonymity indicator.

In some embodiments, the users in a place can exchange chat messageswith each other via a chat utility that is provided in the placeinterfaces. An exemplary embodiment of a chat utility will now bedescribed with respect to the chat window 330 of the exemplary placeinterface 320 shown in FIG. 3D.

As shown in FIG. 3D, the exemplary chat utility or window 330 includesportions 330 a and 330 b. For purposes of clarity, portions 330 a and330 b are referred to herein as the history and live components of thechat window, respectively. The live component 330 b is configured forreceiving chat messages for transmission, and the history component 330a is configured for providing and/or otherwise presenting chat messagesthat are exchanged during a visit to a place (e.g., in the form of achronological log file or transcript). For example, a user 102 ₁interacting with client 120(1) and desiring to exchange a chat messagewith another user 102 _(M) interacting with client 120(M) of a place canenter and/or otherwise provide the message into the live component 330 bof the chat window 330 via an input device (e.g., a keyboard, a stylus,a mouse, etc.) of the client 120(1). Based on detecting the entry of themessage in live component 330 b, client 120(1) presents the message inhistory component 330 a and transmits the message to server 140 forfurther transmission. Based on receiving the message from client 120(1),server 140 transmits the message to client 120(M) based on the IPaddress of client 120(M) stored in on-line status data 230 forpresentation in the history component 330 a of the corresponding chatutility 330.

Usually, chat messages that are entered and/or otherwise provided into alive component 330 b of a chat window 320 are considered publicmessages. As such, server 140 transmits chat messages that are receivedfrom a client 120 via a live component 330 b to all other clients 120 ina place. The chat facility 330 is, therefore, a public chat facilitythat allows all users in a place to chat with each other.

Alternatively and/or in combination, in some embodiments, the users in aplace can exchange private chat messages with each other based ongenerating a private place. In one such embodiment, a user 102 ₁desiring to exchange a private chat message with another user 102 _(M)can select the user 102 _(M) identifier (or other user 102 _(M) indicia)in (i) the people sub-window 324 of the exemplary place interface 320shown in FIG. 3D for the place or (ii) if user 102 _(M) has beendesignated as a friend by user 102 ₁, the exemplary welcome window 310shown in FIG. 3C. Based on receiving the selection, server 140establishes a new place for users 102 ₁ and 102 _(M) (and only users 102₁ and 102 _(M)) based on the schemes previously described herein. Users102 ₁ and 102 _(M) can then exchange private chat messages with eachother based on entering those messages into the live component 330 b ofthe chat utility 330 of the place interface 320 for the new place. Asfurther described herein, the new place can be administered in parallelto, and independently of, the pre-existing place.

In some embodiments, the disclosed systems and methods provide emailaccounts for a place and/or a group of users, e.g., users authorized toaccess the place. Email exchanges between users in a place can beimplemented based on the chat schemes described herein and schemes knownto those of ordinary skill in the art. In some embodiments, the placeinterface can include an email window similar to the chat window 330 ofthe exemplary place interface 320 shown in FIG. 3D. Email account datacan be stored in place data 250, e.g., place log files 275, so thatemails exchanged in a place can be accessed by all users. Storingexchanged chat messages and email messages provides convenient access tosuch messages to future users of a place (e.g., to users who were notpresent in the place and/or were not authorized to access the placeduring the exchanges).

In some embodiments, the users in a place can share content with eachother via the place interface. Such content can include applications,data files, displays, and/or other types of content. Content sharing canbe understood to include the “pushing” of content (e.g., by server 140in system 100) “into view” (e.g., to clients 120 for presentation incorresponding place interfaces). Some types of supported content sharinginclude, but are not limited to, the sharing of pixels in a presenteddata file (e.g., the sharing of pixels in content window 328), thesharing of pixels from a display screen (e.g., the sharing of the pixelson a display screen of a user of system 100), and the sharing of pixelsin an application (e.g., an application executing on a client).

FIGS. 8A and 8B schematically illustrate an example of steps involved inan embodiment of a method for administering content sharing in a place.The embodiment is described with respect content window 328 in theexemplary place interface 320 of FIG. 3D.

As shown in FIG. 8A, a request from a user 102 ₁ interacting with client120(1) for sharing content in a place is received at server 140 insystem 100 (810 in FIG. 8A). In some embodiments, the request can begenerated based on a selection from a pull-down menu 332 in theexemplary place interface 320 shown in FIG. 3D. Based on receiving therequest, server 140 queries, prompts, or otherwise requests client 120to identify the content to be shared (820 in FIG. 8A). In mostembodiments, server 140 requests client 120 to select the content fromamong default types of content. For example, in one such embodiment, thedefault types of content include (i) the content displayed in thecontent window 328 of the exemplary place interface 320 shown in FIG. 3D(e.g., the content of a place data file 260 or user data file 248), (ii)the content displayed on the screen of display device 126 of client120(1) (e.g., the place interface for client 120(1) and the desktop forclient 120(1)), and (iii) the content displayed in an applicationcurrently executing on client 120(1) (e.g., a place interface foranother place and/or an application executing on the desktop of client120(1)). Based on receiving an identification of the content to beshared, server 140 prompts, queries, or otherwise requests client 120(1)to transmit the shared content (830 in FIG. 8A). Based on receiving theshared content, server 140 generates a miniature screen shot or“thumbnail” of the shared content based on schemes known to those ofordinary skill in the art (840 in FIG. 8A) and transmits the miniaturescreen shot of the shared content to client 120(1) and other client(s)120(M) in the place for presentation in the corresponding placeinterfaces (850 in FIG. 8A). For example, in some embodiments, server140 transmits the miniature screen shots to client(s) 120(1) and 120(M)for presentation in the thumbnails 324 a of the people window 324 of theplace, interface 320 shown in FIG. 3D. Server 140 can transmit theshared content to clients 120(1) and 120(M) based on the IP addressesfor those clients stored in on-line status data 230.

Client 120(M) can view the shared content in thumbnail 324 a based onactivating and/or otherwise selecting the thumbnail 324 a. For example,client 120(M) can click on or otherwise designate the thumbnail 324 awith a mouse or other input device. Activation of thumbnail 324 a causesplace interface program(s) 104 and/or 108 to present the shared contentin content window 328. Preferably, shared content is accompanied bytoolbars 328 b and scrollbars 328 c to facilitate editing and navigationof the shared content.

During content sharing, client 120(1) and/or server 140 can detectchanges in the shared content based on schemes known to those ofordinary skill in the art (860 in FIG. 8A). Based on those changes,server 140 can generate an updated miniature screen shot (870 in FIG.8A), and transmit the updated miniature screen shot to client 120(1) andother clients 120(M) for presentation in the corresponding placeinterfaces (880 in FIG. 8A). Also, clients 120(1) and 120(M) and/orserver 140 can update the content window 328 to include the changes.

With reference to FIG. 8B, client 120(1) can terminate content sharingas desired. For example, in one embodiment, client 120(1) can terminatecontent sharing based on a selection of an option from a pull-down menu332 in the exemplary place interface 320 of FIG. 3D. Based on receivinga request to terminate content sharing from client 120(1) (885 in FIG.8B), server 140 transmits instructions that cause clients 120(1) and120(M) to remove thumbnails 324 a in people window 324 (890 in FIG. 8B).

In some embodiments, the users in a place can consecutively edit (e.g.,write to) content being shared with each other (e.g., a data file) viathe place interface. Such consecutive editing involves control ofcontent (e.g., a data file), rather than control of a collaborationplace (e.g., server 140 and/or another component of system 100). FIG. 9Aschematically illustrates an embodiment of a method for administeringconsecutive content editing in a place. The embodiment is described withrespect to content window 328 and the control panel 390 in the exemplaryplace interface 320 of FIG. 3D. As will be understood by those ofordinary skill in the art, the disclosed systems and methods are notlimited to the embodiment shown in FIG. 9A and can administerconsecutive content editing in a place based on features that aredifferent than and/or additional to the features shown in FIG. 9A.

As shown in FIG. 9A, server 140 administers the sharing of a data filebetween user 102 ₁ interacting with client 120(1) and user 102 _(M)interacting with client 120(M) based on the schemes previously describedherein (910 in FIG. 9A). Server 140 associates a write lock on the datafile with an identifier for user 102 ₁ and/or client 120(1), i.e., theuser/client who initiated the content sharing, so that only user 102₁/client 120(1) can edit and/or otherwise write to the data file (920 inFIG. 9A). Server 140 processes requests from the clients 120(1) and120(M) for editing the data file based on the write lock, e.g., based ondetermining whether the identifier of the requesting client isassociated with the write lock for the data file (930 in FIG. 9A).Server 140 denies editing requests from client 120(2) until user 102₁/client 120(1) passes control of the data file. (Usually, a denial of arequest to control a data file is experienced by a user as an inabilityto highlight, grab, or otherwise select a visible portion of the shareddata file presented in the content window 328.)

With continuing reference to FIG. 9A, a request from client 120(1) topass control (e.g., write permission) of the data file to client 120(2)is received at server 140 (940 in FIG. 9A). In some embodiments, client120(1) can generate a request to pass control based on activating thecontrol icon 394 in the control panel 390 of the content window 328shown in the exemplary place interface 320 of FIG. 3D. Client 120(1) canpass control to client 120(2) voluntarily or in reply to a request fromclient 120(2) for the control. Such a request can be generated based onan activation of control icon 394 by client 120(2) and can be pushed byserver 140 to client 120(1) for presentation in the place interface.Based on receiving the request, server 140 releases the write lock forthe data file from its association with the user 102 ₁/client 120(1)identifier (950 in FIG. 9A) and associates the write lock for the datafile with the user 102 ₂/client 120(2) identifier (960 in FIG. 9A).Server 140 then returns to processing requests for control (930 in FIG.9A) until receiving a request to terminate sharing (970 in FIG. 9A).

In some embodiments, the users in a place can concurrently edit (e.g.,write to) content being shared with each other via the place interface.This so-called “co-editing” feature of the disclosed systems and methodsallows clients to simultaneously modify different fields of a data filein a place. For example, in some of such embodiments, each client canconcurrently modify a field of a spreadsheet (e.g., a cell, a row, or acolumn) or a document (e.g., a word, a sentence, or a paragraph).

Usually, the co-editing feature is supported by client-side andserver-side software. On the client side, each client includes at leasttwo types of software applications executing thereon. The first type ofsoftware applications includes applications that are configured formodifying and otherwise interacting with data files. The second type ofsoftware applications includes applications for interfacing the firsttype of software applications to the server. The second type of softwareapplications can include so-called “software development kits” (SDKs)that are known by those of ordinary skill to facilitate the client-sidedevelopment of plug-ins for the first type of software applications.Utilizing SDKs to interface client-side software with the serverobviates the necessity of exposing server-side software to the clients,thereby enhancing the integrity of the server. On the server side, theserver includes software for supporting the co-editing feature, i.e.,software for administering independent data streams from independentclients. The server-side co-editing software is configured formonitoring, tracking and/or otherwise detecting interactions between theclients, monitoring, tracking, and/or otherwise detecting changes toshared content, and advising the clients of and/or otherwisetransmitting to the clients the detected changes. The server-sideco-editing software is further configured for detecting and avoidingco-editing collisions. Such collision detection and avoidance isfacilitated by software for administering data ranges within objects andpermissions or locks associated with those ranges.

Generally, each data file in the disclosed systems and methods includesa lock scheme that determines the extent to which the data file can besimultaneously edited by clients. The lock scheme separates the datafile into one or more parts or sub-parts and associates a lock with eachof those parts. For example, the lock scheme for a word processingdocument can include a lock for each word, sentence, or paragraph withinthe document. As described herein, a lock scheme that associates lockswith different parts of an object allows different clients tosimultaneously edit, i.e., co-edit, those parts.

As will be understood by those of ordinary skill in the art, a lockscheme can associate a single lock with an entire object. While suchlock schemes do not permit co-editing because the lock can be associatedwith only a single client, they do permit consecutive editing and globalcontrol of a data file. Such global control can be useful in scenariosin which one client desires to edit or otherwise modify a place datafile without interference from other clients.

Usually, based upon interfacing of a client to a server, a client-sideplug-in for a software application on the client identifies its lockscheme to the server (i.e., identifies the type and number of locksassociated with the object managed by the plug-in) and requests that theserver administer that lock scheme. For example, a plug-in for a simplechessboard application can indicate to the server that two static locksand one dynamic lock are to be managed, in which the static locks areassociated with the two clients who are “playing” the white and blackpieces, and the dynamic lock is associated with the one of the twoclients who has the turn or opportunity to move a piece.

An illustrative example of the co-editing feature will now be provided.In the illustrative example, first and second clients are sharing a datafile in a place. Those of ordinary skill in the art will understand thatthe disclosed systems and methods are not limited to the example and canimplement co-editing based on features different than and/or additionalto those described in the example.

Based on interfacing to a server, a first client identifies a lockscheme for a data file to the server, in which each field of the datafile is associated with a lock. Subsequently, the first client requestspermission to edit a field of the data file. In reply, the serverdetermines whether the field is locked or otherwise unavailable to thefirst client. Based on determining that the field is not locked, theserver grants permission to the first client and updates a database oflocks for the data file to represent the association of a lock on thefield with the first client. Thereafter, the second client requestspermission to edit the same field of the data file. Since the lock onthat field is associated with the first client, the server deniespermission to the second client. Denial of permission to edit a fieldcan manifest itself to the second client as an inability to highlight,grab, or otherwise “touch” the designated field with a user inputdevice. Some time later, the first client requests permission to editanother field. Once again, the server determines whether that otherfield is locked and, as appropriate, grants permission to the firstclient and updates the database of locks for the data file to reflectthe lock on that other field. Additionally, the server releases the lockon the field originally edited by the first client, thereby allowing thesecond client to edit that field.

In some embodiments, the server modifies one or more portions of thecollaboration place interfaces of the first and second clients so as todenote, indicate, and/or otherwise illustrate features of the lockscheme. For example, in some of such embodiments, the server modifiesthe display of the data file being co-edited in the content window ofthe collaboration place interfaces to indicate fields that are locked(e.g., by other users). Such a display scheme can reduce user confusionand/or frustration when requests to edit otherwise locked fields aredenied and/or otherwise unsuccessful.

As mentioned above, a software development kit may be provided inconnection with a virtual collaboration environment to facilitate anopen architecture so that, for example, companies who develop their ownsoftware products can layer and combine their software functionalitywith a collaboration place and extend the range of their abilities. Forexample, illustrative steps involved in implementing such anarchitecture or functionality are shown in FIG. 9B. At step 912, asoftware development kit such as software development kit for thirdparty applications may be distributed in association with acollaboration application such as an application for providing acollaboration place. At step 914, a software data interface such as anapplication program interface or a plug-in is implemented that isadapted to interact with software developed by the software developmentkit and provide a communications interface with the collaborationapplication. At step 916, an application is implemented on a client thatinteracts with the collaboration application via the interface. Theapplication may be an application that is developed and implementedprivately by a customer of the collaboration software who, for example,intends to maintain the software internal to the company. At step 918,the software collaboration application interacts with the application toaugment the functionality of the application. For example, theapplication may be manipulated to control user or computer interactions,to centrally store information on interactions, to maintain a relateddatabase, etc.

In one embodiment, a user desktop application can benefit from thecollaborative infrastructure. For example, with reference to FIG. 9C, atstep 922, a software resident application implemented on a user computerto provide collaboration tools such as a collaboration place can beimplemented for a plurality of users. At step 924, the collaborationapplication may be supported by implementing a network (e.g., Internet)connection (e.g., using TCP/IP) with a server that is configured tointeract with the software resident collaboration application forproviding collaboration among the users. At step 926, a third partyapplication (e.g., another software resident application) is implementedon user platforms (e.g., to coexist in executable form on the usercomputers). (As used herein, the term user platform can be understood toinclude computer software and/or hardware for accessing a collaborationplace.) At step 928, interaction between the users in the third partyapplication is managed via the server supporting the software residentapplication for collaboration. As such, the features of thecollaboration application and supporting server can be extended to otherdesktop applications. By managing the other application, theuser-interactions, software client to client interactions, or operationof the other applications can controlled or managed via communications(e.g., sending messages) between the other application and the server.In some respect, the server and the related collaboration softwareprovide a framework for implementing and running the other applicationon user platforms. At step 932, activity in the third party applicationcan be synchronized by the server (e.g., via a back channel connection)such as to provide live interaction within the third party applicationbetween users. Step 932 is directed to managing or updating the otherapplication (e.g., managing or updating the displayed or accessibleinformation in that application for the users) synchronously. Step maybe, if desired, a component of step 928 (e.g., to implement synchronousfeature). Thus, interactions can be viewed live by participants. At step934, information on the users participating in the interaction (e.g.,identity information such as authentication or tracking information) orinformation on the interactions themselves are stored (e.g., centrallystored). The information stored can be related to the activity on theserver (e.g., can be information (e.g., files) that resulted fromactivity on the server to support the other application and is storedfor later retrieval by the users who participated in the activity.

Illustrative examples of “co-editing” or partnered control overapplications and documents are illustratively shown in FIGS. 9D-9F. InFIG. 9D, co-editing is enabled by implementing a control button that canbe selected to take control over a document or application in a client'scontent window. As shown, client #1 and #2 are each in a collaborationplace in which they are participating in a collaboration using contentwindows 936 and 938 to co-edit the same document. Content windows 936and 938 may include the features and functionality of the collaborationinterfaces illustratively described in connection with FIGS. 3A-3G. Theapplication running in content windows 936 and 938 may be a text editor,word processor, or other application that is integrated with thecollaboration place as part of the executable software of the place ormay be a third party application that is adapted to allow suchfunctionality. FIG. 9E is illustrative of simultaneous co-editing. Inthis case, client #1 and client #2 are provided with an opportunity tointerface with the same document or application by controlling access tocomponents of the document or application. As shown, client #1 isediting paragraph #12 of a document at the same time as client #2 isediting paragraph #13. FIG. 9F illustrates an infrastructure forproviding live interaction. As shown, server 946, collaborationapplications 952 implemented on the user platform of client #1 andcollaboration application 962 implemented on user platform of client #2are configured to communicate via Internet connections 948 to provide acollaboration system. Each client may further include a third partysoftware application interface that is developed for example by acompany with intranet clients #1 and #2. The third party softwareinterface 958 and 964 are configured to interact with collaborationapplications 956 and 962 to provide collaboration between client #1 and#2 in the third party application. The interaction may be displayed andupdate in real time (i.e., as events happen) in the interface via thecollaboration infrastructure (e.g., using a back channel connection withthe server to push event updates).

In another aspect, one of the users involved in co-editing of a documentmay be given the option to halt the work of another user in thatdocument. This control may be attributed to a particular user based, forexample, on identifying the user who contributed the document to thecollaboration or who created the document. This type of control permitsa user to maintain control over the consecutive or simultaneousco-editing of document by others.

In some embodiments, the disclosed systems and methods support audio(e.g., voice) communications among users in a place. FIG. 10schematically illustrates an exemplary system for supporting voicecommunications in a place. As shown in FIG. 10, users 1002 _(i)interacting with respective clients 1020(i) can access a place based oncommunicating with server 1040 over network 1010 based on schemesdescribed herein. Clients 1020(1) and 1020(2) are voice-enabled clients,i.e., they are associated with peripheral devices for converting soundinto electrical signals (e.g., microphones) and peripheral devices forconverting electric signals into sound (e.g., speakers). Clients1020(M−1) and 1020(M) are not voice-enabled clients, but respectiveusers 1002(M−1) and 1002(M) can interact with conventional telephones1085 (e.g., plain old telephone service (POTS) telephones, wirelesstelephones, etc.). At least three different types of voice conversationscan be established in a place have voice-enabled and non-voice-enabledclients: (i) conversations between two or more voice-enabled clients,(ii) conversations between two or more non-voice-enabled clients, and(iii) conversations between one or more voice-enabled clients and one ormore non-voice-enabled clients. Some exemplary schemes for establishingthese types of voice conversations will now be described. As will beunderstood by those of ordinary skill in the art, the disclosed systemsand methods are not limited to the exemplary schemes and can beimplemented to support voice communications in a place based on schemesincluding different and/or additional features than those describedherein.

Voice communications can be established in a place based on receiving arequest from one or more users in the place. For example, in someembodiments, a request from a first user to establish a voiceconversation with a second user can be received at server 1040. In onesuch embodiment, the request can be generated based on a selection froma puh-down menu 332 in the exemplary place interface 320 shown in FIG.3D. Based on receiving the request, server 1040 determines whether thefirst and/or second users are interacting with voice-enabled clientsbased on schemes known to those of ordinary skill in the art. Forexample, in one embodiment, server 1040 can prompt, query, and/orotherwise request the respective first and second clients to identifyand/or otherwise indicate their voice capabilities.

Based on determining that the first and second users are interactingwith voice-enabled first and second clients (e.g., clients 1020(1) and1020(2)), server 1040 establishes a voice connection between the clientsbased on Voice over Internet Protocol (VoIP) or another packet-switchedprotocol known by those of ordinary skill in the art to support voicecommunications. Server 1040 mediates the voice communications betweenthe first and second users (e.g., to provide VoIP call-controlfunctionality to the respective clients, such as call muting, callwaiting, and call disconnecting), records the communications, andsynchronizes the communications with interactions between the first andsecond users in the place so as to generate audio-synchronized place logfiles 275.

Based on determining that the first and second users are interactingwith non-voice-enabled first and second clients (e.g., clients 1020(M−1)and 1020(M)), server 1040 selects a conference call line for associationwith the first and second users (e.g., selects a line from among one ormore such lines associated with the place and/or with system 100),determines a password/passcode for the conference call line, transmitsthe password/passcode to the first and second users, and activatessoftware agent 1060 to connect to the conference call line. Based onserver 1040 and/or agent 1060 detecting the connection of the first andsecond users to the conference call line, agent 1060 records thecommunications between the first and second users. Server 1040synchronizes the recorded communications with interactions between thefirst and second users in the place so as to generate audio-synchronizedplace log files 275.

Based on determining that the first and second users are interactingwith a first voice-enabled client and a second non-voice enabled client,respectively, (e.g., clients 1020(1) and 1020(M−1)), server 1040 againselects a conference call line for association with the first and secondusers, determines a password/passcode for the conference call line,transmits the password/passcode to the second user, and activatessoftware agent 1060 to connect to the conference call line. Also, server1040 establishes and mediates a VoIP connection (or another type ofconnection for supporting voice communications) between the first clientand the agent 1060. Based on server 1040 and/or agent 1060 detecting theconnection of the second user to the conference call line, agent 1060records the communications between the first and second users. Server1040 synchronizes the recorded communications with interactions betweenthe first and second users in the place so as to generateaudio-synchronized place log files 275. Such a scheme allowsvoice-enabled clients and non-voice enabled clients to participate in aunified voice conversation.

Based on determining that the first user is interacting with a firstvoice-enabled client and the second user is interacting with a secondpartially voice-enabled client (e.g., a client having speakers, but nota microphone), server 1040 establishes a VoIP connection between theclients. Such a connection, which allows the second client to listen tovoice communications from the first client, can be useful in a scenarioin which the first user is giving a presentation to the second user in aplace.

Voice communications can also be established in a place by default. Forexample, in some embodiments, a place can be said to be “wired forsound,” e.g., the server administering the place can establish VoIPand/or other types of voice-supporting connections between voice-enabledclients based on detecting the entrance of those clients into the place.

Voice communications can also be established in a place retroactively.For example, in some embodiments, first and second users can establish aPOTS conference call and then provide the conference call line andpasscode/password to the server administering a place, so that theserver can activate a software agent to record the communications.

As will be understood by those of ordinary skill in the art, voiceand/or other types of audio communications can be selectively recorded.For example, in some embodiments, voice and/or audio recording can beselected by a user at one or more intervals, e.g., during a call set-up,during a meeting set-up, and/or during a meeting (“on-demand”). In someof such embodiments, based on receiving a selection of audio recordingfrom a client participating in a conversation, server 1040 can alertand/or otherwise advise other clients in the conversation of therecording and/or provide options to the other clients for pausing and/orotherwise terminating the recording (e.g., to go “off the record”).

In some embodiments, server 1040 can provide data identifying theparticipants in a voice conversation, data identifying the speakingparticipant(s), and other data describing the voice conversation toclients 1020(i) for presentation in the place interfaces based onschemes described herein and schemes known to those of ordinary skill inthe art. For example, in some embodiments, server 1040 can determine theidentity of a speaking user in a voice conversation based on comparingone or more voice communications received from the user with one or morestored voiceprints for users of system 100. Also for example, in someembodiments, server 1040 can instruct clients 1020 to activate one ormore icons in respective place interfaces to designate a speaking user(e.g., flash, illuminate, and/or otherwise highlight one or more iconsassociated with the speaking user).

In some embodiments, server 1040 can recommend and/or otherwise suggestthat users in a place establish a voice conversation with each otherbased on detecting one or more criteria. For example, in one suchembodiment, based on comparing the frequency and/or duration ofexchanged chat messages with a threshold, server 140 can query, prompt,and/or otherwise request the first and second users to establish a voiceconversation. Of course, server 1040 can be configured to recommendand/or otherwise suggest a voice conversation based on differentcriteria, such as criteria indicative of whether the first and secondusers prefer to communicate via chat and/or other criteria that will beapparent to those of ordinary skill in the art.

Video can also be implemented, for example, in conjunction with audio tofurther enhance collaboration. Video may be live video of collaborationparticipant or of other content of interest to the current place. Videocan implemented to be displayed in a collaboration place interface.

One or more of the collaboration activities previously described hereincan be understood more generally in terms of a so-called “activitythread” that describes how users work together in a place. Some examplesof activity threads include instant and scheduled meetings. Eachactivity thread is associated with an activity plan and an activityrecord. Some features of activity threads, activity plans, and activityrecords will now be described.

An activity plan includes data describing a type of an associatedactivity thread (e.g., a meeting), data identifying the name of theactivity thread, and data identifying participants in the activitythread. The participants in the activity thread can be selected and/orotherwise determined based on the schemes described herein. For example,in some embodiments, identifiers for the participants can be selectedfrom and/or searched for based on the identifiers and/or contactinformation for the members of a place, the members of system 100,and/or other contacts (e.g., contacts in an email application, such asMicrosoft® Outlook®).

In some embodiments, an activity plan also includes data identifying oneor more of the following features of an activity thread: description;start time; duration; end time; participant instructions (e.g., audio,video, and/or multi-media instructions); agenda; and/or one or morethread options (e.g., de-activating one or more single-user activitiesand determining one or more guest privileges). Usually, the agenda of anactivity thread includes one or more agenda items for considerationand/or completion by the participants of the thread. For example, anagenda item can include a name, an objective, a duration, a statusindicator (e.g., pending, completed, confirmed, cancelled), notes (e.g.,notes associated with a time of entry and/or an identifier of anauthor), and/or other features (e.g., attached content (such as datafiles or other objects (e.g., Internet pages) or links thereto). In someembodiments, the agenda item can be associated with one or morepresenters (e.g., one or more participants responsible for the agendaitem) and, in some of such embodiments, only the one or more presenterscan edit and/or otherwise modify an agenda item. In some embodiments,the agenda items are ordered based on importance and can be re-orderedby their respective presenters.

An activity record includes data based on the activity plan (e.g., asummary of the data included in the activity plan) and data based oninteractions in the respective activity thread. Activity records arestored in place log files 275 for subsequent reference based on theschemes described herein. In some embodiments, an activity record can begenerated based on detecting a termination of an activity plan. Forexample, in some of such embodiments, an activity record can begenerated based on detecting a selection of an end activity icon from apull-down menu 332 in the exemplary place interface 320 shown in FIG.3D.

Activity threads can be automatically or selectively established. Insome embodiments, activity threads are automatically established basedon the entrance of a user into a place. Alternatively, in someembodiments, activity threads are established based on the generation ofan activity plan by a user in a place. Regardless, each activity threadincludes one or more displays (e.g., one or more of the windows in theexemplary place interface 320 shown in FIG. 3D) and, in someembodiments, an accompanying audio channel.

Some examples of activity threads will now be described. Those ofordinary skill in the art will recognize that the disclosed systems andmethods are not limited to the examples of activity threads describedherein and can be implemented to support additional and/or differenttypes of activity threads than those described herein.

A first example of an activity thread is a presentation that includesone active user (“the presenter”) and one or more passive users (“thelisteners”). In the first example, the place interfaces of the listenersare configured by server 140 based on the activity plan to include apersonal display (e.g., content window 328) and a presentation display(e.g., a podium display), each of which displays can be viewed andnavigated by the listeners based on the schemes described herein. Thepresenter can disable the personal displays of the listeners as desired(e.g., to focus the attention of the listeners), can generate one ormore additional presentation displays, and can select and/or otherwisedetermine the presentation screen being viewed by the listeners.

A second example of an activity thread is a spontaneous thread thatincludes two or more active users in a place. In the second example, theplace interfaces of the users include the displays previously describedherein (e.g., the displays in the exemplary place interface 320 of FIG.3D) for supporting chat and/or other types of collaboration activities.

A third example of an activity thread includes a scheduled meeting thatincludes two or more active users in a place. In the third example, anagenda is generated and content is associated with the agenda (e.g.,data files or objects or links thereto). Based on the activity plan,server 140 configures the place interfaces of the users to include apresentation display, an agenda display, and a personal display. In someembodiments, server 140 provides a time indicator for presenting a timeallotted to and/or otherwise remaining for the agenda and/or an agendaitem. Based on detecting a termination of the activity thread, server140 generates a summary of the activity thread, transmits the summary tothe users (e.g., via email), and stores the summary and data based onthe activity plan in an activity record.

In some embodiments, the disclosed systems and methods support guidedcollaboration schemes that facilitate collaboration among users in aplace. As known by those of ordinary skill in the art, guidedcollaboration schemes can blend relatively structured and unstructuredenvironments together. For example, one type of guided collaborationscheme includes one or more separate phases and one or more tasks withineach phase, in which the phases are managed in a relatively structuredway and the tasks are managed in a relatively unstructured way.

In some embodiments, the disclosed systems and methods support guidedcollaboration schemes that include one or more workflows. A workflow canbe established by a user in a place (e.g., a manager of other users) andcan be associated with one or more projects for completion by otherusers (e.g., employees) in the place. Each project can be assigned toone or more of the users and can be associated with one or more tasksand one or more applications and/or one or more data files forcompleting the tasks. Usually, only the user who established theworkflow can edit and/or otherwise modify the workflow. The tasks, datafiles, and applications associated with a project are presented to theemployees in a place via respective place interfaces. Based oncompletion of a task, an employee can be presented with differentapplications and/or different data files in the respective placeinterface for completion of another task.

In some embodiments, the disclosed systems and methods support guidedcollaboration schemes that include one or more templates. For example,in one such embodiment, the disclosed systems and methods can present a“home page” for a place in a place interface based on detecting theentrance of a user into the place. Such a home page can include linksand/or other shortcuts to data describing events in the place (e.g.,links to what is new in the place and what other users have been doingin the place).

As previously indicated, the client-server infrastructure of thedisclosed systems and methods supports data persistence in a place. FIG.11 schematically illustrates exemplary types of data persistence in aplace. As will be understood by those of ordinary skill in the art, thedisclosed systems and methods are not limited to the types and/or theorganizations of data persistence shown in FIG. 11 and can beimplemented to support additional and/or different types and/ororganizations of data persistence than those shown in FIG. 11.

As shown in FIG. 11, the exemplary types of data persistence includeuser-perspective data persistence and place-perspective datapersistence. User-perspective data persistence refers to user-side data,such as user data 1110. Examples of user data 1110 include user skindata 1135 and user data files 1148. Place-perspective data persistencerefers to place-side data, such as place data 1150. Examples of placedata 1150 include place data files 1160 and place log files 1175. Insome embodiments, place log files 1175 can include one or more of chatsummaries, place summaries, and meeting objects. Features of place logfiles 1175 and their contents will now be described.

As previously described herein, place log files 1175 include datagenerated based on interactions between users in a place. Place logfiles 1175 can be generated based on the schemes described herein andthe schemes described in U.S. patent application Ser. No. 09/942,161,the contents of which application are expressly incorporated byreference herein in their entirety.

As known by those of ordinary skill in the art, conventional datamanagement systems that support versioning and audit trail functionalityallow users to determine the state of one or more data files (or, moregenerally, objects, as that term is understood by those of ordinaryskill in the art) at one or more prior times. Usually, such databasemanagement systems provide versioning and audit trail functionalitybased on an archive paradigm, in which versions of data files that arearchived are divorced from their metadata (e.g., their time-sensitivecontext) so as to reduce data storage constraints.

In contrast to conventional data management systems, the disclosedsystems and methods support metadata-rich storage schemes that allowusers to access time-dependent views of a place. For example, in someembodiments, the log files 1175 for a place can be viewed by anauthorized user via a log file interface. The log file interface caninclude a primary display and one or more secondary displays similar tothose in the exemplary place interface 320 shown in FIG. 3D, one or morecontrol icons for controlling the viewing of the log file (e.g., iconsfor rewinding, playing, pausing, and/or fast forwarding the log file),and a time or other status bar for denoting a relative time in the logfile. In some embodiments, one or more of the control icons can besupplemented by and/or replaced with a slider on the time bar. In onesuch embodiment, based on receiving a selection of a time from a user,the disclosed systems and methods provide a view of the place in the logfile interface that shows the state of all objects (including all datafiles and displays) in the place at the selected time based on themetadata associated with those objects. The time-dependent views of aplace can be generated based on schemes known to those of ordinary skillin the art and the schemes described in U.S. patent application Ser. No.09/942,161, the contents of which application are expressly incorporatedby reference herein in their entirety.

In some embodiments, the log file interface can be used as a searchutility to find and/or otherwise locate objects associated with a place.For example, a user desiring to find a data file that was associatedwith a place at a prior time can select the view of the place at thattime in the respective place log files 1175 and then navigate that view(e.g., play or fast forward the view) to a later time (e.g., a presenttime) to determine the disposition of the object.

In some embodiments, server 140 stores chat messages that are exchangedby clients 120 in a place (e.g., via the live components 330 a of thechat utilities 330 in the exemplary place interfaces 320) in a place logfile 1175 to facilitate review of the chat messages. Server 140associates the place log file 1175 with the place identifier for theplace and stores the place log file 1175 in place data 1150. In someembodiments, server 140 stores the place log file 1175 based ondetecting a termination event (e.g., based on detecting a logout of allof the participants from a place). Alternatively and/or in combination,in some embodiments, server 140 stores the place log file 1175 andupdates the place log file 1175 at intervals (e.g., periodic intervalsand/or intervals based on a quantity of data in the exchanged chatmessages).

Storing chat messages in a place log file 1175 allows users to reviewthe chat messages during subsequent visits to the place. For example, insome embodiments, based on receiving a selection of history icon 331 inthe chat window 330 of the exemplary place interface 320 shown in FIG.3D, server 140 can provide the place log file(s) 1175 for the place toclient 120(1) for presentation in the place interface. In one suchembodiment, the place log file(s) 1175 can be presented in the form of adirectory or index of log files, in which each log file includes a chatsummary or, alternatively, a chronological transcript generated during avisit to the place.

In some embodiments, server 140 can generate summaries of activity in aplace. For example, server 140 can generate summaries including databased on one or more of the following based on schemes known to those ofordinary skill in the art: total size of data files uploaded to theplace during a time interval, total size of data files downloaded fromthe place during a time interval, meetings in the place during a timeperiod and features thereof (e.g., elapsed meeting minutes), chats inthe place during a time period of features thereof (e.g., quantities oftext bits exchanged in a place by individual users), conversations inthe place during at time period and features thereof (e.g., elapsedvoice minutes), and visits to the place (e.g., by users and/or guests).Such summaries can be provided to administrators of system 100 (e.g.,managers of users of system 100) for evaluation.

In some embodiments, server 140 records data based on interactionsbetween users in a meeting in a meeting object, associates the meetingobject with a meeting name identifier and a place identifier, and storesthe meeting object in place log files 1175. In some of such embodiments,each meeting object can be associated with one or more permissions forallowing participants in the meeting to access and/or otherwise view themeeting object (e.g., during the meeting and/or after the termination ofthe meeting). In one such embodiment, users in a place who are notinvited to a meeting but who can otherwise detect the meeting (e.g.,based on one or more of the peripheral vision schemes described herein)can request access to the meeting a meeting administrator and/or ameeting invitee via server 140.

As known by those of ordinary skill in the art, several separate classesof objects can be associated with a meeting (or, more generally, acollaboration activity): an invitation, an agenda, notes, attachmentsand/or handouts, and minutes (e.g., audio, textual, or video). Thedisclosed systems and methods support the collapse of these severalclasses into a single class. Some of the benefits of this collapseinclude enhanced accessibility, mutability, navigation, andsearchability of meeting content, an ability to accesscontextually-related objects (e.g., to interpret interrelationshipsamong objects), and an ability to access a convenient template forcloning a meeting (e.g., to obtain a starting point for a follow-upmeeting).

In some embodiments, the disclosed systems and methods implement thelinking of time-based objects described in U.S. patent application Ser.No. 09/942,161, the contents of which application are expresslyincorporated by reference herein in their entirety. In some of suchembodiments, navigation and searchability of meeting objects are furtherenhanced by the time-based object features.

In some embodiments, the disclosed systems and methods manage meetingobjects based on the agendas associated therewith. For example, in onesuch embodiment, a user who initiates and/or otherwise establishes ameeting can identify agenda items for the meeting and associate one ormore objectives with each of the agenda items. The objectives caninclude business or other types of objectives that are supported by theagenda items. Subsequently, the user can identify results related to thebusiness objectives based on searching the meeting object and/or otherrelated objects.

In some embodiments, the disclosed systems and methods support cloningof meetings (or, more generally, places). As known by those of ordinaryskill in the art, several factors can be relevant to the efficiency of ameeting. Some of these factors include whether the parameters of themeeting (e.g., participants, agenda, duration, and recurrence) aresuitable for satisfying meeting objectives, whether the meetingobjectives are communicated to meeting participants, and whether themeeting participants have endorsed and/or otherwise determined that theselected parameters are suitable for satisfying the meeting objectives.The disclosed systems and methods fulfill each of these factors bystoring meeting objects for prior meetings and enabling the cloning ofprior meetings to generate new meetings. For example, in someembodiments, a meeting organizer can clone a prior successful meeting toestablish a starting point for a later meeting. In some of suchembodiments, the meeting organizer can modify one or more features ofthe cloned meeting based on feedback from participants in the priormeeting.

In some embodiments, the disclosed systems and methods allow one or moreparticipants in a meeting to be “invisible” to (i.e., undetectable by)other participants in the meeting. As known by those of ordinary skillin the art, one or more meeting invitees may not be expected toparticipate in and/or otherwise review the results of the meeting. Thedisclosed systems and methods allow such invitees to observe the meetinginvisibly based on the peripheral vision schemes described herein, jointhe meeting at a suitable juncture (e.g., when a topic of interest ispresented), and review the results of the meeting in the meeting object.

In some embodiments, the disclosed systems and methods support theinclusion and annotation of notes in meeting objects to memorialize datadescribing a meeting (e.g., the agenda items considered and the progressmade and/or decisions taken on those items during the meeting). Forexample, in some of such embodiments, the notes in a meeting object canbe formatted into one or more tables or other similar data structureswith columns for names of agenda items, descriptions of the agendaitems, and decisions on the agenda items. Also for example, in some ofsuch embodiments, different notes in a meeting object can be associatedwith each other (e.g., a note related to a first agenda item can becross-referenced to a note related to a second agenda item). In one suchembodiment, the associations can be selected and/or otherwise determinedbased on drag-and-drop functionality of one or more input devices of aclient (e.g., a mouse).

In some embodiments, the disclosed systems and methods can providedifferent views of meeting objects (e.g., the notes included in themeeting objects) during a meeting to advise meeting participants of thestatus and progress of a meeting. For example, in some of suchembodiments, detailed views showing all meeting notes and/or summaryviews showing abstracted meeting notes can be provided to meetingparticipants via respective place interfaces. Also for example, in someof such embodiments, the views can provide indications of one or moremeeting features, e.g., whether the meeting is being recorded for laterreference and whether a voice conversation is in progress.

The disclosed systems and methods can implement a variety of schemes toindex and search for data files and other objects associated with aplace, as the term objects is understood by those of ordinary skill inthe art. Features of some of these schemes are now described.

In some embodiments, one or more software application programs 108residing on server 140 are configured for identifying one or moreindexable features of objects associated with a place. Alternatively, insome embodiments, the objects themselves can define their indexablefeatures based on functionality provided by SDKs known to those ofordinary skill in the art. Server 140 can index and store the identifiedindexable features in one or more indices in place data 250.

In some embodiments, server 140 can provide structured and/orunstructured search capabilities for objects associated with a place.For example, in some of such embodiments, server 140 permits users todefine and/or otherwise determine categories of searchability. Also forexample, in some of such embodiments, server 140 interprets queries forobjects in a place context, so that queries for objects received from auser in a place are interpreted to be queries for the objects in theplace.

In some embodiments, server 140 can search one or more of the supportedapplications in a place for content, such as chat applications, emailapplications, content viewing and editing applications, and/or otherapplications. Additionally, in some of such embodiments, server 140 canalert and/or otherwise notify a user based on identifying desiredcontent. For example, in one such embodiment, server 140 can search forreferences to a user identifier in an active chat and notify the userbased on the detecting one or more references.

In some embodiments, server 140 can interpret queries based onchronological and/or other time-sensitive data included therein. Forexample, in one such embodiment, server 140 can search for meetings in aplace in which picture data files were uploaded into the place within atime interval of a mention of the word “beautiful” in a chat applicationin the place.

In some embodiments, server 140 can interpret search criteria includedin queries to detect acceptable or unacceptable content, such as contentconsistent or inconsistent with one or more statutory and/or regulatoryschemes. Additional features of ensuring compliance with statutory andregulatory schemes are described in U.S. patent application Ser. No.09/590,099, the contents of which application are expressly incorporatedby reference herein in their entirety.

In some embodiments, the disclosed systems and methods provide one ormore guides or tools to facilitate searching. For example, in some ofsuch embodiments, the disclosed systems and methods can provide apublishing tool (e.g., via the exemplary place interface 320 shown inFIG. 3D) that allows a user of a place to generate a guide or index tothe content in the place. Such a guide can include one or more linksand/or shortcuts to data files and other objects, which links orshortcuts can be supplemented with annotations or other comments.

The disclosed systems and methods can implement a variety of securityschemes to enhance user privacy in a place and/or to inhibit and/orprevent interception of data by unauthorized entities. Features of someof these schemes are now described.

As previously described herein, in some embodiments, server 140 updatesuser data 210 and place data 250 based on an entry (e.g., a login event)of a new user into a place and provides the updated place data tocurrent users in the place. For example, in some of such embodiments,server 140 can provide updated place participant identifiers 270 to thecurrent users, so as to alert and/or otherwise notify the current usersof the entry of the new user. Alternatively, in some embodiments, server140 provides updated place participant identifiers 270 only to thosecurrent users who are identified in the friend data 245 for the newuser. As such, the new user can remain “invisible” to the other currentusers in the place, thereby enhancing the privacy of the new user.

In most embodiments, clients and servers in the disclosed client-serverinfrastructure can form secure connections with each other to inhibitinterception of data exchanged therebetween by third parties. Suchsecure connections can include VPN connections and/or other types ofsecure connections known to those of ordinary skill in the art.

The disclosed systems and methods can concurrently administer a varietyof different places. In some embodiments, the disclosed systems andmethods can generate a so-called “worldview” of currently administeredplaces. Such a worldview can present interrelationships between placesbased on common users in those places and detect migrations of usersfrom place to place. For example, in some of such embodiments, thedisclosed systems and methods can detect user visits to and activity incurrently administered places during one or more time intervals. Assuch, the disclosed systems and methods can detect relatively hot orcold places, e.g., places having relatively high levels of immigrationor emigration. In some embodiments, the worldview can be presented toadministrators and/or other types of users of system 100 with zoomingcapabilities. For example, in some of such embodiments, the worldviewcan be zoomed from an outer level showing places and theirinterconnections to an inner level showing the features of a place.

FIG. 13A schematically illustrates an embodiment of a method forsearching for and reviewing a selected object using a time line feature.As will be understood by those of ordinary skill in the art, thedisclosed systems and methods are not limited to the embodiment shown inFIG. 13A pertaining to searching for and reviewing objects, and suchsearches and review can be based on features that are different and/orthat are in addition to those depicted in FIG. 13A.

Referring to FIG. 13A, a request from a user 1302 interacting with aclient is received by the system 100 to select a place. The systemserver queries databases 1304 for the data associated with the selectedplace, and presents the data to the user, for example, in the placeinterface 320 (see FIG. 3D). The system then receives a request from theclient regarding the time line feature 1306 concerning an object, aselected date and/or the state of a collaboration place at a particularpoint in time in the past. The system queries databases and presents1308 the data associated with the selected object, date, or state ofcollaboration and presents it in the place interface. The system thenchecks to see if the client selected a play feature 1310, and if so,queries the databases and presents 1312 all the data associated with aselected range of dates and the object in the place interface.

The time line feature can, for example, permit a user to make selectionspertaining to a relative time, and the system then providescorresponding views of the state of all related objects based on storedmetadata associated with each version of the object. A things window mayinclude an archive of objects in a place or a collaboration place, whichmay be displayed as a folder or available in compressed format. The timeline feature may be used to review an object as it appeared on aparticular date, and to review the state of all related objects as ofthat date. A metadata-rich version of the object is provided, whichpermits a user to review various related attributes, such as who workedon a particular document on a selected date. The time line feature alsoincludes a “play” option that permits a user to review how a document orother object has changed over a selected time range, including theability to review associated metadata concerning the object that maysupply further useful information. For example, in an implementation,the time line feature can be used with any of the place data files inthe things window 326, such as with a particular folder or document. Forexample, if a document is created by the collaborative efforts of aplurality of users in a particular place at a particular time, it maysubsequently be moved, deleted, renamed or misplaced by one or manyusers. One of the collaborators who wishes to locate the document aftersuch changes have been made will have difficulty finding the documentusing traditional search methods, such as by querying the document byname, content or other metadata, because such methods will not work ifthat document has been drastically altered or deleted. Moreover, theuser wishing to locate a specific document may not recall suchinformation, only recalling that it was created in a certain place on orabout a certain date. Thus, the time line feature can be utilized tosearch for the document, and to observe how the document was changedover time.

FIGS. 13B and 13C depict a screen shot of a place interface 1320 similarto that shown in FIG. 3D, but it includes the time line feature that maybe utilized by a user to find a document, for example. As will beunderstood by those of ordinary skill in the art, the methods andsystems are not limited to the embodiment shown in FIGS. 13B and 13C,and the time line feature can be offered to a user in a different mannerthan that depicted in FIGS. 13B and 13C. In this example, the userremembers that a document was created with respect to a particularplace, and thus selects that place so that it appears with all of theassociated data. The user then clicks on the time line icon 1322 toobtain a time line slider 1324 as shown. In this embodiment, the timeslider 1324 includes a related pop-up calendar 1326 to help the userpinpoint a date and time. The user can utilize the time line slider andcalendar to select a date and time that the user recalls viewing orworking on the document of interest. In particular, the cursor can bemoved over the time slider and the right mouse button held down to moveor drag the time line button 1325 up and down along a track thatrepresents time, which may include the beginning date when the place orobject was created up to the present date. As the time line sliderbutton 1325 is moved along the path, the data presented in the placeinterface window and the calendar view 1326 changes to present a view ofthe documents, other objects available on that date and time, a set ofobjects in the collaboration place or entire contents of a collaborationpalce. When the mouse button is released, the time line slider button1325 is located somewhere along the track, and the data that was presentat that time and in that place is shown. In this particular example, theuser selected Nov. 10, 2003 as the date of interest. The user can thenidentify and chose a particular document, other object, sets of objects,or the collaboration to review, for example. The timeline feature can,thus, provide context to state of an objects in place and its evolutionin that place.

The user may also utilize the play feature by clicking on a play icon1328 associated with the time line slider 1324. The play featureautomatically moves the time slider button 1325 along the track from theselected date to the present, which causes the place interface todisplay changing views of the selected document and related objectsduring that time period. The user can also use the calendar feature 1322to rewind to a particular date to find a particular view of an object.For example, the calendar could be used to review the data and/orobjects available in a specific place that was present last week, andthen fast forward to the present time to see how the data and/or objectswere manipulated, who changed any or all of the data, and where suchdata went in the system.

A time line feature may include other aspects. The feature can includedisplays that permit a previous time with the specificity of hours,minutes, or seconds. Thus, the user can specify for the software theexact date and time and the software in response, display a selectedobject, set of objects, or a place as it existed at the selected time.For example, a user can speficy a time and date for one or more (e.g. aset of) artifacts that resulted form collaboration in a content windowand in result the system will display the artifact(s) (including theinformation contained in them) as of that date. Thus, the user canactually see the contents of object as it stood at that time toconsider, for example, its evolution. In one aspect, the focus can bedirected to the contents of folder or a window and how its contentevolved. Time stamps and indexing can be used in implementing suchfeatures.

Thus, the time line feature can provide information such as who viewed aparticular document, and/or who edited that document, and at what timeor times a particular person viewed and/or changed the document. Suchinformation is often needed to answer questions concerning complianceand regulatory matters. The time line feature provides a quick and easymeans to find the answers to such questions.

A feature that can be provided for a collaboration place or othercollaboration application is a private interface that is available to auser when interacting in a virtual collaboration environment accessibleby other users. For example, with reference to FIG. 14A, illustrativesteps are provided for providing a private interface or “personalplace.” At step 1400, a private interface is displayed in acollaboration application when a user is interacting with acollaboration tool of the application. A private interface may bedisplayed with content that is available to the user but is not viewableby others who may also be interacting with the collaboration tool (e.g.,not available to other users in a collaboration place). At step 1402,the user is provided with the ability (e.g., option buttons, movablefiles, active content, etc. in the private interface) to use orcontribute content from the user's private interface to the activity inthe current collaboration tool. Such a contribution is preferablyprovided without opening access to other content in the user's privateinterface. At step 1404, a user may, if desired, provide temporaryaccess to the private interface or content in the interface to anotheruser (e.g., access that only exists while the collaboration session withthe other user is still open).

In another aspect, a user can be privately provided with informationnecessary for the user's consideration in influencing the user'sactivity within the collaboration application. For example, withreference to FIG. 14B, at step 1406, a private place, which is based ona collaboration place, is displayed in conjunction with a collaborationwindow of a collaboration application. At step 1408, private informationrelated to the user is displayed in the private place (e.g., displayspersonally selected documents, applications, files, objects, etc.). Step1408 may include steps 1410 for displaying a list of collaborationplaces related to the user. At step 1412, visual cues in associationwith the information in the private place is displayed to privatelyalert the user or to influence the user's activity in the collaborationapplication. Step 1412 may include step 1414 for displaying informationin the private place on current activity related to places of interestto the user.

For example, with reference now to FIG. 14C, collaboration applicationwindow 1416, which is based on the collaboration place interfaceillustratively shown in FIGS. 3A-3G, include things window 1418 forstoring files or folders that are part of the current collaborationplace. Things window 1418 is shown to include private place 1420. Eachuser in the collaboration application can have his or her own suchinterface that follows the user in every collaboration activity withinthe collaboration application. Private place 1420 can for exampleinclude the user's documents, software tools, places, or other objectsselected by the user. If desired, the current user #3 can initiateinteraction with user #2 by moving the icon for user #2 over an item inprivate place 1420. In response, interface 1422 can be displayed (e.g.,without exiting interface 1416). Interface 1422 implements temporaryauthorization for user #2 to provide access to an item for the privateplace of user #3. In interface 1422, user #2 and user #3 can view and,for example, collaborate with respect to the item in private place 1420,which user #3 selected by dragging and dropping user #2 on that item.Once the session is over, user #2 preferably will not longer have notaccess to any content of the private place of user #3.

A number of different visual cues can be provided to a user in a privateplace. For example, with reference to FIG. 14D, things window 1424 caninclude private place 1428. Private place 1428 includes documents bar1430 which can be expanded to display a directory of the current user'spersonal documents and files. Private place 1428 also includes placesbar 1432 and includes list of places displayed under bar 1432. The listof places is identified to be displayed in private place 1428 based, forexample, on the user's frequency of visits to a place, the user'smembership in a place, key places that are pertinent to that user's rolein the organization, or based on other relational characteristics thatare automatically or manually selected. The list may also be displayedbased on priority of information that is displayed in association withthe place. Information is displayed in association with the places toalert or influence the user's actions. For example, as shown, withrespect to Project A place, the system is informing the user that ameeting is about to start in that place in ten minutes. With respect toProject B place, the system is displaying information alerting the userthat his supervisor has just entered that place. With respect to ProjectC place, the system is informing the user that there are currently sixpeople in that place. With respect to Project D place, the system cansimply provide information indicating that the level of activity in thatplace is currently high. The level may be determined based on variousfactors such as number of people in the place, the rate of activity inthe place, an increase in downloaded documents in that last hour, orother factors.

The disclosed systems and methods can provide user-based presenceawareness and place-based presence awareness. User-based presenceawareness refers to the ability of a user in a place to detect theactivity of other users in the place. For example, as previouslydescribed herein, a first user in a place can detect the activity of asecond user in the place based on an activity indicator and/or aminiature screen shot for the second user. Place-based presenceawareness refers to the ability of a user in a place to detect theactivity of users in other places. User-based presence awareness andplace-based presence awareness are implemented based on one or moreperipheral vision schemes. Some features of place-based presenceawareness and the corresponding accompanying peripheral vision schemeswill now be described.

Generally, the disclosed systems and methods allow a user to construct aso-called “virtual geography” of one or more places and monitor, track,and/or otherwise detect the activity occurring in those places. Usually,the places in the virtual geography include places of which the user isa member. In some embodiments, however, the places in the virtualgeography include places in which the user is not a member.

FIG. 15 schematically illustrates an embodiment of a method forproviding place-based presence awareness. The method is described withrespect to the administration of places by server 140 in system 100. Aswill be understood by those of ordinary skill in the art, the disclosedsystems and methods are not limited to the embodiment shown in FIG. 15can provide place-based presence awareness based on features that aredifferent than and/or additional to the features shown in FIG. 15.

As shown in FIG. 15, server 140 generates activity data for each placethat it currently administers (e.g., for each place with one or moreusers logged or otherwise entered into the place) (1510 in FIG. 15). Theactivity data for a place can include one or more of the following: databased on the users currently entered and/or otherwise logged into aplace (e.g., the number of users in the place and/or their useridentifiers), data based on the activity of each of the users in theplace (e.g., activity indicators or thumbnails for each user in theplace), and data based on multi-user activities in the place (e.g., dataidentifying the type of each multi-user activity in the place (such asinstant meeting, polling, chatting, emailing, sharing of content, andvoice conversation) and the numbers and/or identifiers of the usersparticipating in each such multi-user activity. Server 140 associatesthe activity data for each place with the corresponding place identifier225 (1520 in FIG. 15) and stores the activity data in place data 250(1525 in FIG. 15) and updates the activity data at one or more intervals(e.g., periodic intervals) (1530 in FIG. N).

A request from a user 102 interacting with client 120 and desiring toview the activity data for one or more of the currently administeredplaces (e.g., one or more places in which the client is participatingand/or otherwise present and/or one or more places in which the clientis not participating and/or not otherwise present) is received at server140 (1540 in FIG. 15). In some embodiments, the request can be generatedbased on a selection from a pull-down menu 332 in the exemplary placeinterface 320 shown in FIG. 3D. Based on receiving the request, server140 prompts, queries, and/or otherwise requests client 120 to identifythe one or more places of interest (1550 in FIG. 15).

In some embodiments, system 100 allows a user to view the activity dataonly for places in which the user is a member. In some of suchembodiments, therefore, server 140 queries databases 150 to find placeidentifiers 255 associated with the user identifier 215 for user 102 andprompts, queries, and/or otherwise requests client 120 to select amongthose place identifiers.

Alternatively, in some embodiments, system 100 allows a user to view theactivity data for places in which the user is a member and for places inwhich the user is a non-member but nonetheless has permission to viewthe activity data. Such a permission can be granted by an administratorof system 100, an originator of a place, and/or a user of a place. Insome of such embodiments, therefore, server 140 queries databases 150 tofind (i) place identifiers 255 associated with the user identifier foruser 102 and (ii) place identifiers 255 associated with viewingpermissions for user 102 and then prompts, queries, and/or otherwiserequests client 120 to select among those place identifiers.

Subsequently, server 140 receives a selection and/or an identificationof one or more place identifiers 225 from client 120(1) (1560 in FIG.15). In most embodiments, server 140 associates those place identifiers255 with the user identifier 215 (1565 in FIG. 15) and stores the useridentifier 215 and the thusly associated place identifiers 255 in userdata 210 for subsequent retrieval (1570 in FIG. 15). For example, server140 can store such information as a default set of places for which toprovide activity data to user 102. Of course, in some embodiments, user102 can select and/or otherwise identify a different set of defaultplaces. For example, in some of such embodiments, user 102 can selectthe default places to include the previous n places visited by the user(e.g., the previous five (5) places).

Server 140 provides the activity data associated with the selected placeidentifiers to client 120 for presentation (1580 in FIG. 15). In someembodiments, server 140 provides the activity data to client 120 forpresentation in the corresponding place interface, e.g., in a window inthe place interface reserved for presenting activity data for places.For example, in one such embodiment, server 140 provides the activitydata to client 120 for presentation in a window similar to the peoplewindow 324 in the exemplary place interface 320 of FIG. 3D. Such awindow can list and/or otherwise identify the place identifiers andpresent indicia of the corresponding activity data. Also for example, inone such embodiment, server 140 provides the activity data to client 120for presentation in the personal place of the user.

FIG. 16 shows an exemplary places activity window for presentingactivity data associated with one or more places. As shown in FIG. 16,the window 1600 can form part of a place interface 1610 (denoted bydashed lines in FIG. 16) and can present an icon 1620 for each place ofinterest to a user. In some embodiments, activation of the icon 1620 fora place (e.g., by moving a cursor over the icon 1620) can cause activitydata for the corresponding place to be displayed. As will be understoodby those of ordinary skill in the art, the activity data for a place canbe presented in a variety of different formats. Some of these formatsare shown in FIG. 16 and include one or more of a numerical indicator1630 representative of the number of users in a place, a colored orotherwise shaded indicator 1640 representative of a type ofcollaboration activity in a place, a listing and/or other identificationof the users in the place 1650, and/or a listing or other identificationof the users in the place participating in a collaboration activity1660.

In some embodiments, the activity data provided by server 140 can bepresented in the form of the previously described worldview thatpresents interrelationships among places as well as activity dataassociated with those places. As such, the activity data can be providedfor a desired number of places in the worldview. For example, theactivity data can be provided for a single place, a neighborhood of twoor more places, and a world of all currently administered places. Alsofor example, the activity data can be provided for all places of whichthe client is currently a member, a first subset of the places of whichthe client is a member, and a second subset of the places of which theclient is a member, in which the first subset is larger than the secondsubset. In one such example, more types of activity data can be providedin the all places view than in the first subset view and, separately,the second subset view, and more types of activity data can be providedin the first subset view than in the second subset view.

In some embodiments, the disclosed systems and methods can advise,alert, and/or otherwise notify the users of a place that the activitydata for the place is being detected by a user of system 100. Such aninverse view allows the users in the place to “reverse-detect” thepresence of the observing user. For example, in some of suchembodiments, the disclosed systems and methods can provide to the usersin a collaboration place data based on the quantity of requests receivedfrom other users for the activity data of the place. In someembodiments, the disclosed systems and methods allow the users in theplace to invite the observing user into the place and/or otherwisesignal to the observing user the status of the activity in the place.

Another feature enhancement for collaboration is to locally store orshadow server data such as content available through the things windowor private place interface. This feature will for example permit afolder to exist on a user's computer that shadows content in acollaboration place.

In another enhancement, a user may be provided with offline access todata associated with a collaboration place. For example, a copy of afile from the things window of a collaboration place may be stored in auser's computer for access and manipulation after the user has exitedthe collaboration-place. In another example, a copy of the things windowcan be stored locally for access by the collaboration place interface bya user when the interface is not connected to the server. This, forexample, implements the interface with related features when a user isnot network connected, is not in the respective place, or has chosen towork in a solitary fashion.

If desired, a collaboration place may include links to otherapplications, systems, sites, or places. A single sign-on may beimplemented for the content of the collaboration place. Thus, once auser has entered a particular place of which he is a member (e.g., bypassing through security), his access can be extended to the systems,applications, sites, or places that are linked to that place (e.g.,linked because they are related in substance to the activities of thecurrent place). As such a user who has logged into a place isautomatically logged into the linked sites, systems, applications, orplaces. One way to accomplish this is to store login information for theuser (e.g., user-id, password) and automatically apply that informationwhen the user selects the link for a desired application, site, system,or places available through the place.

As mentioned above, in some embodiments, systems and methods areimplemented that inform a user of a collaboration application of eventsof interest to the user. A user may be informed by way of alert withinthe collaboration place or through an indicator that appears on theuser's desktop (e.g., a floating overlay over the active desktopapplication that rises and drops out of view). The alerts may betriggered by system-configured threshold activity or events that areexpected to be of interest to users. In another aspect, each user can beprovided with options for configuring the alerts or information thatwill be communicated to that user in response to an activity ofinterest. For example, the user can select an option to be informed if aplace that he is a member of currently contains six people and one ofthose people has a particular title or role within the user'sorganization. Another example is for the user to setup the collaborationapplication to inform the user when five people have a meeting thatlasts for more than 60 minutes and involves 5 or more files in theagenda.

A thing type object is an additional type of object that has certainattributes. A thing type object can provide a work object that supportscollaboration in many different respects. It has attributes that permitsusers to open the object and collaborate synchronously “live” andasynchronously (e.g., after the live session has ended). It provides atool by which live collaboration can be saved and continued throughasynchronous collaboration. It can also provide the ability to send theobject to another user via e-mail and continue the collaboration onanother server.

In some embodiments, the disclosed systems and methods can support oneor more thing types that facilitate collaboration. The thing type can bean object that allows for both synchronous and asynchronousinteractions, combining features of publishing, asynchronousdiscussions, IM, and note taking. The thing type can support chat,blogs, wikis, discussion groups, and other collaborative activities, asthe foregoing terms are understood by those of ordinary skill in theart. It can, for example, incorporate support primary features of blogs,wiki's, and instant messaging.

In some embodiments, a thing type can be generated based on one or moreof the following features: defining the data that the thing type wouldmanipulate (e.g., for a blog, user identification, blog entry, title,date-time stamp, etc.), defining the granularity and nature of eventsfor distribution to clients (e.g., for blogs, defining what types ofchanges will cause change notifications), implementing a new thing typeon the client(s) in system 100 to display the updated data, and modifythe clients (e.g., the collaboration place interfaces) to update thedisplay when change notifications arrive.

A thing type object can be provided in a collaboration place. Forexample, an interface can be displayed in which a user can select toopen or create a thing type object. In response, the content window orsome other window may display the object, which may include pre-setareas for user entry such as a title, or other parameters. Moreover, itincludes areas for content insertion of a greater size such agenda,notes, outline, document writing, figures, drawings, task items, etc.Once for example displayed in a content window, users can collaborate ina live session to generate details as the work on the subject (e.g.,enter agenda, notes on a subject, bullets for a presentation)progresses. The resultant of the live session can be saved and the itsexistence can be reflected with an icon or some file type indicator infor example the things window. The icon on indicator may reflect that itis a special object type. The saved object can later be opened by othersor the original participant to add comments, revisions, additions,deletions, etc. to the information in the object. Thus, for example, acontinuous working file that is for example unattached to a particulartype of collaborative activity can exist (e.g., not tied to a meeting).Users can add notes or remarks to a particular information in the objector can pick up the object for further “live” discussions. Thecollaboration application can have a publication functionality that oncefor example the participant are happy the results of their collaborationin a thing type object can publish their work (e.g., generate a MS Worddocument, an HTML document, an XML document, etc.). Information frommultiple types of collaborative activity in a collaboration place (e.g.,chat and generating an agenda) can be saved as part of the object. Forexample, chat communications or content information displayed inconjunction with a thing type object may be saved as part of the object.

Another illustrative and non-limiting example follows. Users A and Bmeet in a collaboration place and use the thing type to take notes asthey collaborate on a working outline for a technology strategyproposal. Users A and B leave the notes in the collaboration place forcomment and review by other users. At various intervals, other users canreview and comment on the notes (e.g., by inserting comments directlyinto the notes). Subsequently, users A and B (and/or other users) meetin the collaboration place to review and concurrently edit the notes andcomments to generate a finished outline for the proposal. The finishedoutline is then posted in the collaboration place as a charter.

In some embodiments, the disclosed systems and methods can implement oneor more schemes to manage and/or optimize display screen real estate.For example, in some embodiments implementing graceful escalationfeatures, the disclosed systems and methods can rebalance and/orredistribute the presentation data for display in an escalatedcollaboration place interface based on forming and/or otherwise openingone or more windows or panels within the place interface, as opposed toopening additional windows external to the place interface and/oradditional instances of the place interface itself. Also for example, insome of such embodiments, the display screen real estate in acollaboration place interface can be managed to provide one or more ofthe following features: simultaneous display of four panels (e.g., panelfor display of content (e.g., content window), panel for display of chat(e.g., chat window), panel for display of data files in the repositoryor database (e.g., things window), and panel for providing activity dataabout people in the place (e.g., people window)); each of the fourpanels can be opened or closed by a user; the size of each panel can bemodified by the user (e.g., based on adjusting a horizontal and/or avertical dimension of the panel); preferably, the people and thingswindows will be disposed in a vertically aligned relationship; and,preferably, the content and chat panels will be placed in a verticallyaligned relationship. In at least some of such embodiments, the defaultsizing of one or more of the four panels (or, more generally, any panelor display in a collaboration place interface) can be based on the typesand/or quantities of data to be displayed in the panels. For example,panels displaying greater numbers of types of data than other panels canbe allotted greater default amounts of screen space to enhancereadability. Also for example, panels displaying greater quantities ofdata of the same type as other panels can be allotted greater defaultamounts of screen space to enhance readability.

Thus, improved systems and methods for collaboration can be provided.Some of the advantages of the systems and methods of the presentinvention can include, among others, providing collaboration softwareenhancements on an on-demand or as needed basis on a real-time basis tousers during collaboration, providing the necessary software toolsconsistent with the type, state, or level of current real-timecollaboration, and augmenting an enterprise space of individual users toprovide collaboration techniques that parallel in-person collaboration.

In accordance with the principles of the present invention, an object ofthe technology is to allow collaboration software enhancements on anon-demand or on as needed basis. Another object is to provide thenecessary software tools consistent with the type, state, or level ofcurrent collaboration. Other objects of the technology are to augment anenterprise space of individual users to provide collaboration techniquesthat parallel in-person collaboration. Other objects are evident fromthe figures and specification for systems and methods illustrativelyprovided herein.

The systems and methods described herein are not limited to a hardwareor software configuration; they can find applicability in many computingor processing environments. The systems and methods can be implementedin hardware or software, or in a combination of hardware and software.The systems and methods can be implemented in one or more computerprograms, in which a computer program can be understood to include oneor more processor-executable instructions. The computer programs canexecute on one or more programmable processors, and can be stored on oneor more storage media readable by the processor, comprising volatile andnon-volatile memory and/or storage elements.

The computer programs can be implemented in high level procedural orobject oriented programming language to communicate with a computersystem. The computer programs can also be implemented in assembly ormachine language. The language can be compiled or interpreted.

The computer programs can be stored on a storage medium or a device(e.g., compact disk (CD), digital video disk (DVD), magnetic tape ordisk, internal hard drive, external hard drive, random access memory(RAM), redundant array of independent disks (RAID), or removable memorydevice) that is readable by a general or special purpose programmablecomputer for configuring and operating the computer when the storagemedium or device is read by the computer to perform the methodsdescribed herein.

Unless otherwise provided, references herein to memory can include oneor more processor-readable and -accessible memory elements and/orcomponents that can be internal to a processor-controlled device,external to a processor-controlled device, and/or can be accessed via awired or wireless network using one or more communications protocols,and, unless otherwise provided, can be arranged to include one or moreexternal and/or one or more internal memory devices, where such memorycan be contiguous and/or partitioned based on the application.

Unless otherwise provided, references herein to a/the processor anda/the microprocessor can be understood to include one or more processorsthat can communicate in stand-alone and/or distributed environment(s)and can be configured to communicate via wired and/or wirelesscommunications with one or more other processors, where such one or moreprocessor can be configured to operate on one or moreprocessor-controlled devices that can include similar or differentdevices. Use of such processor and microprocessor terminology can beunderstood to include a central processing unit, an arithmetic logicunit, an application-specific integrated circuit, and/or a task engine,with such examples provided for illustration and not limitation.

Unless otherwise provided, use of the articles “a” or “an” herein tomodify a noun can be understood to include one or more than one of themodified noun.

While the systems and methods described herein have been shown anddescribed with reference to the illustrated embodiments, those ofordinary skill in the art will recognize or be able to ascertain manyequivalents to the embodiments described herein by using no more thanroutine experimentation. Such equivalents are encompassed by the scopeof the present disclosure and the appended claims.

For example, the disclosed systems and methods are not limited toimplementation in a client-server infrastructure, but can be implementedin one or more infrastructures known to those of ordinary skill in theart, such as, but not limited to, peer-to-peer infrastructures.

Also for example, the disclosed time line features are not limited toapplication in a collaboration place, but can be applied to one or moresystems and/or software applications known to those of ordinary skill inthe art, such as, but not limited to, document management systems.

It should be understood that the above description of the invention andspecific examples, while indicating preferred embodiments of the presentinvention, are given by way of illustration and not limitation. Manychanges and modifications within the scope of the present invention maybe made without departing from the spirit thereof, and the presentinvention includes all such changes and modifications.

1. A computer implemented method for collaboration, comprising:receiving requests from first and second clients to establish aplurality of collaboration places; based on the requests: establishingat least one collaboration place, wherein the collaboration placepersists independent of user presence in the collaboration place, andforming network connections between the collaboration place and each ofthe first and second clients; and associating the collaboration placewith first and second collaboration place interfaces executing on therespective first and second clients, each of the first and secondcollaboration place interfaces including a primary display forpresenting a primary type of data, each of the first and secondcollaboration place interfaces configured for being escalated bymodifying a complexity of the interfaces in synchronization with one ormore user activity in the collaboration place; providing from adatabase, escalation triggers indicating collaboration involving aplurality of different secondary data types, to each of thecollaboration place interfaces; using escalation triggers that compriserules implemented in software logic in the collaboration placeinterfaces to: (a) detect a collaboration aspect of an action taken by auser, (b) identify one of the different plurality of secondary types ofdata based on the collaboration aspect, (c) match an appropriatesecondary display to the identified secondary type of data, thesecondary display for presenting the secondary type of data to enable anew form of client collaboration activity, (d) send a request inresponse to identifying at least one of the different secondary types ofdata, and (e) perform, based on sending the request, seamless escalationto the secondary display in each of the collaboration place interfaces.2. The method of claim 1 wherein the primary type of data includes datarelated to at least one of a chat application and an instant messengerapplication.
 3. The method of claim 2 wherein the secondary type of dataincludes data related to at least one of an application for processingaudio data, an application for processing graphic data, an applicationfor processing multimedia data, an application for processing text data,and an application for processing video data.
 4. The method of claim 2further comprising escalating, based on receiving another request fromthe first client, the first collaboration place interface to includeanother secondary display for presenting data related to at least one ofan application for processing audio data, an application for processinggraphic data, an application for processing multimedia data, anapplication for processing text data, and an application for processingvideo data.
 5. The method of claim 2 further comprising escalating,based on receiving another request from the first client, the firstcollaboration place interface to include another secondary display forpresenting data related to the clients connected to the collaborationplace.
 6. The method of claim 2 further comprising escalating, based onreceiving another request from the first client, the first collaborationplace interface to include another secondary display for presenting datarelated to data files associated with the collaboration place.
 7. Themethod of claim 1 farther comprising associating the database with acollaboration of the clients.
 8. The method of claim 7 furthercomprising storing objects from the collaboration place interfaces inthe database for a later resumption of another collaboration.
 9. Themethod of claim 1, wherein the rules of the escalation triggers comprisea template, and wherein a sequence of templates are configured to becombined into the template to provide escalation to the secondarydisplay associated with a final template in the sequence withoutescalating through intermediate displays associated with an intermediatetemplate in the sequence.
 10. The method of claim 9, wherein thetemplate is associated with a type of task or a type of industry. 11.The method of claim 1 farther comprising escalating the secondcollaboration place interface to include another secondary display basedon a request from the first client.
 12. The method of claim 1 furthercomprising escalating the first and second collaboration interface whenone of the first or second clients takes an action of pulling an objectinto their collaboration place interface.
 13. The method of claim 1farther comprising displaying additional displays in the collaborationplace interfaces that each implement a different collaboration tool. 14.The method of claim 1 wherein the secondary display is for acollaboration tool that is a portion of a resident applicationimplemented for each client to provide the collaboration placeinterfaces.
 15. The method of claim 1 further comprising displaying athings window, a content window, and a chat window in the collaborationplace interfaces.
 16. The method of claim 1 farther comprisingdisplaying a private interface for the first client as part of the firstcollaboration place interface.
 17. The method of claim 1 furthercomprising storing a record of activity between the clients.
 18. Themethod of claim 1 wherein one or more collaboration interfaces includesunifying data.
 19. The method of claim 1, wherein the secondary datatypes include a combination of at least two of a type of the useractivity, a type of collaboration participants, a type of a documentcurrently being shared, a link within the document, or a taskassignment.
 20. The method of claim 1, wherein providing from thedatabase, the escalation triggers further comprises providing theescalation triggers over a network.
 21. A system for collaboration,comprising: a computer that is configured for: receiving requests fromfirst and second clients to establish a plurality of collaborationplaces; based on the requests: establishing at least one collaborationplace, wherein the collaboration place persists independent of userpresence in the collaboration place, and forming network connectionsbetween the collaboration place and each of the first and secondclients; and associating the collaboration place with first and secondcollaboration place interfaces executing on the respective first andsecond clients, each of the first and second collaboration placeinterfaces including a primary display for presenting a primary type ofdata, each of the first and second collaboration place interfacesconfigured for being escalated by modifying a complexity of theinterfaces in synchronization with one or more user activity in thecollaboration place; providing from a database, escalation triggersindicating collaboration involving a plurality of different secondarydata types, to each of the collaboration place interfaces; usingescalation triggers that comprise rules implemented software logic inthe collaboration place interfaces to: (a) detect a collaboration aspectof an action taken by a user, (b) identify one of the differentplurality of secondary types of data based on the collaboration aspect,(c) match an appropriate secondary display to the identified secondarytype of data, the secondary display for presenting the secondary type ofdata to enable a new form of client collaboration activity, (d) send arequest in response to identifying at least one of the differentsecondary types of data, and (e) perform, based on sending the request,seamless escalation to the secondary display in each of thecollaboration place interfaces.
 22. The system of claim 21 wherein theprimary type of data includes data related to at least one of a chatapplication and an instant messenger application.
 23. The system ofclaim 22 wherein the secondary type of data includes data related to atleast one of an application for processing audio data, an applicationfor processing graphic data, an application for processing multimediadata, an application for processing text data, and an application forprocessing video data.
 24. The system of claim 22 wherein the computeris further configured for escalating, based on receiving another requestfrom the first client, the first collaboration place interface toinclude another secondary display for presenting data related to atleast one of an application for processing audio data, an applicationfor processing graphic data, an application for processing multimediadata, an application for processing text data, and an application forprocessing video data.
 25. The system of claim 22 wherein the computeris further configured for escalating, based on receiving another requestfrom the first client, the first collaboration place interface toinclude another secondary display for presenting data related to theclients connected to the collaboration place.
 26. The system of claim 22wherein the computer is further configured for escalating, based onreceiving another request from the first client, the first collaborationplace interface to include another secondary display for presenting datarelated to data files associated with the collaboration place.
 27. Thesystem of claim 21 wherein the computer is further configured forassociating the database with a collaboration of the clients.
 28. Thesystem of claim 27 wherein the computer is further configured forstoring objects from the collaboration place interfaces in the databasefor a later resumption of another collaboration.
 29. The system of claim21 wherein the computer is further configured for escalating the secondcollaboration place interface to include another secondary display basedon a request from the first client.
 30. The system of claim 21 whereinthe computer is further configured for escalating the first and secondcollaboration interface when one of the first or second clients takes anaction of pulling an object into their collaboration place interface.31. The system of claim 21 wherein the computer is further configuredfor displaying additional displays in the collaboration place interfacesthat each implement a different collaboration tool.
 32. The system ofclaim 21 wherein the secondary display is for a collaboration tool thatis a portion of a resident application implemented for each client toprovide the collaboration place interfaces.
 33. The system of claim 21wherein the computer is further configured for displaying a thingswindow, a content window, and chat window in the collaboration placeinterfaces.
 34. The system of claim 21 wherein the computer is furtherconfigured for displaying a private interface for the first client aspart of the first collaboration place interface.
 35. The system of claim21 wherein the computer is further configured for storing a record ofactivity between the clients.
 36. The system of claim 21 wherein one ormore collaboration interfaces includes unifying data.
 37. A computerreadable storage medium having machine-readable instructions thereon forperforming steps for collaboration, the steps comprising: receivingrequests from first and second clients to establish a plurality ofcollaboration places; based on the requests: establishing at least onecollaboration place, wherein the collaboration place persistsindependent of user presence in the collaboration place, and formingnetwork connections between the collaboration place and each of thefirst and second clients; and associating the collaboration place withfirst and second collaboration place interfaces executing on therespective first and second clients, each of the first and secondcollaboration place interfaces including a primary display forpresenting a primary type of data, each of the first and secondcollaboration place interfaces configured for being escalated bymodifying a complexity of the interfaces in synchronization with one ormore user activity in the collaboration place; providing from adatabase, escalation triggers indicating collaboration involving aplurality of different secondary data types, to each of thecollaboration place interfaces; using escalation triggers that compriserules implemented in software logic in the collaboration placeinterfaces to: (a) detect a collaboration aspect of an action taken by auser, (b) identify one of the different plurality of secondary types ofdata based on the collaboration aspect, (c) match an appropriatesecondary display to the identified secondary type of data, thesecondary display for presenting the secondary type of data to enable anew form of client collaboration activity, (d) send a request inresponse to identifying at least one of the different secondary types ofdata, and (e) perform, based on sending the request, seamless escalationto the secondary display in each of the collaboration place interfaces.38. The computer readable medium of claim 37 wherein the primary type ofdata includes data related to at least one of a chat application and aninstant messenger application.
 39. The computer readable medium of claim38 wherein the secondary type of data includes data related to at leastone of an application for processing audio data, an application forprocessing graphic data, an application for processing multimedia data,an application for processing text data, and an application forprocessing video data.
 40. The computer readable medium of claim 38, thesteps farther comprising escalating, based on receiving another requestfrom the first client, the first collaboration place interface toinclude another secondary display for presenting data related to atleast one of an application for processing audio data, an applicationfor processing graphic data, an application for processing multimediadata, an application for processing text data, and an application forprocessing video data.
 41. The computer readable medium of claim 38, thesteps further comprising escalating, based on receiving another requestfrom the first client, the first collaboration place interface toinclude another secondary display for presenting data related to theclients connected to the collaboration place.
 42. The computer readablemedium of claim 38, the steps farther comprising escalating, based onreceiving another request from the first client, the first collaborationplace interface to include another secondary display for presenting datarelated to data files associated with the collaboration place.
 43. Thecomputer readable medium of claim 37, the steps further comprisingassociating the database with a collaboration of the clients.
 44. Thecomputer readable medium of claim 43, the steps further comprisingstoring objects from the collaboration place interfaces in the databasefor a later resumption of another collaboration.
 45. The computerreadable medium of claim 37, the steps farther comprising escalating thesecond collaboration place interface to include another secondarydisplay based on another request from the first client.
 46. The computerreadable medium of claim 37, the steps further comprising escalating thefirst and second collaboration interface when one of the first or secondclients takes an action of pulling an object into their collaborationplace interface.
 47. The computer readable medium of claim 37, the stepsfarther comprising displaying additional displays in the collaborationplace interfaces that each implement a different collaboration tool. 48.The computer readable medium of claim 37 wherein the secondary displayis for a collaboration tool that is a portion of a resident applicationimplemented for each client to provide the collaboration placeinterfaces.
 49. The computer readable medium of claim 37, the stepsfurther comprising displaying a things window, a content window, andchat window in the collaboration place interfaces.
 50. The computerreadable medium of claim 37, the steps further comprising displaying aprivate interface for the first client as part of the firstcollaboration place interface.
 51. The computer readable medium of claim37, the steps further comprising storing a record of activity betweenthe clients.
 52. The computer-readable medium of claim 37 wherein one ormore collaboration interfaces includes unifying data.